Powershell
Sheron Norsworthy
I saw the exact command in another forum and the user said that Dropbox uses it for updates. Can anyone confirm this? Is there somewhere online with more information on the powershell commands that Dropbox uses?
Did this post help you? If so please give it a Like below.
Did this post fix your issue/answer your question? If so please press the 'Accept as Best Answer' button to help others find it.
Still stuck? Ask me a question! (Questions asked in the community will likely receive an answer within 4 hours!)
We have run into this exact same behavior, which was detected with our endpoint software. Is it normal for DropBox to operate in this way? I'm concerned that someone may have maliciously hijacked powershell to dump credentials to a dropbox account.
I'm working on deploying a single-machine base ArcGIS Enterprise 11.2 deployment on an EC2 instance in AWS using PowerShell DSC. It appears that everything is working properly except the federation step, which hangs and never proceeds nor produces an error. Any thoughts on what might cause the federation to hang? Or any ideas on troubleshooting steps/observations?
Thank you for the feedback and direction @ArchitSrivastava. I was able to identify the cause for this issue and found a workaround. See Base Enterprise Deployment Hangs During Federation Esri/arcgis-powershell-dsc Discussion #515 (g....
Thanks for getting back to me. I am using PowerShell DSC, not Chef. That being said, I finally got an error after the step hung for about an hour indicating that token generation was unsuccessful. The exact message is:
PowerShell DSC resource ArcGIS_Federation failed to execute Test-TargetResource functionality with error message: Unable to retrieve Portal Token for 'portaladmin' from Deployment
'EC2AMAZ-RQ2AG6M'
AWS Cloud Formation Templates to Deploy ArcGIS Enterprise run behind the scenes Chef scripts that you can check the logs under C:\Chef. I do not use PowerShell DSC on my deployments but I wonder if it also calls Chef scripts inside the machine that you can check the logs. I hope this clarifies.
I appreciate the feedback. I realize that AWS CloudFormation templates use CINC under the hood. I'm not using CloudFormation templates. PowerShell DSC does not rely on CINC/Chef. I've opened a case with Support Services to see whether they have any ideas.
I would like to request if you can share more details like the deployment architecture and which JSON you are utilizing from the sample configs available in the Github link mentioned below (as these are latest and upgraded for 11.2):
Additionally, there also seems to be a known and replicated issue with Powershell and 11.1 deployment. The issue seems to produce a similar error. It seems that the same works with 11.0 but has some issues since 11.1, to help understand more details, I am share the Github discussion URL below:
I have a workflow that clones and fills in Excel templates with requests for another department. Said department takes PDFs, so I mashed together a Powershell script that converts the Excel files in a specified folder into PDFs:
When I found & ran it, I realized Alteryx was not opening and running the generated script; specifying the working directory allowed the powershell script to run as expected. In this case, my workflow lives in a local Test folder.
Hi,
You should add some requirements in the powershell-sdk readme, like the powershell version that must be at least 6.2, the fact we need PSYaml as well (sometime the server is not able to get it and you have to install it manually).
I have been using Powershell for many years, but I am a complete newbie to Github, and I would like to contribute to the SDK. I found and reported a bug (Issue #78). I forked the repository, fixed the issue, tested, and would like to do a pull request, but I am at a loss on how to do that. Can someone walk me through how to submit my change?
My username on Github is BeejCyr
PowerShell is an object-oriented automation engine and scripting language with an interactive command-line shell that Microsoft developed to help IT professionals configure systems and automate administrative tasks.
Built on the .NET framework, PowerShell works with objects, whereas most command-line shells are based on text. PowerShell is a mature and well-proven automation tool for system administrators employed in both IT departments and external entities, such as managed service providers, because of its scripting capabilities.
PowerShell originated as a proprietary offering that was only available on Windows. Today, PowerShell is available by default on most recent Windows systems; simply type "powershell" into the Windows search bar to locate the PowerShell app. In 2016, Microsoft open sourced PowerShell and made it available on Linux and macOS.
Microsoft designed PowerShell to automate system tasks, such as batch processing, and to create system management tools for commonly implemented processes. The PowerShell language, similar to Perl, offers several ways to automate tasks:
Admins can use PowerShell to handle a wide range of activities. It can extract information on OSes, such as the specific version and service pack levels. "PowerShell providers" are programs that make data contained in specialized data stores accessible at the command line. Those data stores include file system drives and Windows registries.
PowerShell also serves as the replacement for Microsoft's Command Prompt, which dates back to DOS. Microsoft, for example, made PowerShell the default command-line interface (CLI) for Windows 10 as of build 14791. PowerShell's role as a command-line shell is how most users become acquainted with the technology.
The most appealing reason to use any kind of CLI is the potential for precise and repeatable control over a desired action or task flow that is difficult, or even impossible, to replicate with a traditional GUI.
Consider using a GUI to perform an intricate task. It can involve clicking buttons, moving sliders, selecting files from multilayered menus and other actions. GUIs were designed to be comfortable for humans to use, but they can be time-consuming, cumbersome and error-prone -- especially when a task must be repeated hundreds or thousands of times.
In contrast, PowerShell offers a CLI with a mature and detailed scripting language that enables a user with rudimentary programming skills to craft a detailed set of specific instructions, or a script, for a desired task. The task can be just about anything, from finding a desired file to describing a desired state configuration for the system or other systems. Once the script is created, it can be saved as a file and executed with a click, enabling the same task to be repeated exactly the same way for any number of repetitions. Different scripts can also be chained together to create complex and highly detailed tasks.
These simple-sounding characteristics are absolutely essential for automation and scalability -- letting the computer do the work as much as is needed for the environment. Thus, PowerShell can help system administrators perform complex and highly repetitive tasks with a high level of automation and accuracy that a GUI simply can't replicate.
Discoverability. Users can discover PowerShell's features using cmdlets, such as Get-Command, which creates a list of all the commands -- including cmdlets and functions -- available on a given computer. Parameters can be used to narrow the scope of the search.
Help capabilities. Users can learn more about PowerShell principles and particular components, such as cmdlets, through the Get-Help cmdlet. The -online parameter provides access to help articles on the web if available for a particular topic.
Remote commands. Admins can perform remote operations on one or multiple computers, taking advantage of technologies such as Windows Management Instrumentation and WS-Management. The WS-Management protocol, for example, lets users run PowerShell commands and scripts on remote computers.
Pipelining. With PowerShell, commands can be linked together through the pipe operator, symbolized as . This approach lets the output from a given command become the input for the next command in the pipeline sequence. The PowerShell pipeline lets objects, rather than text strings, flow from one cmdlet to another. This powerful capability is important for complex and detailed automation scripts.
With PowerShell 4.0, Microsoft introduced a configuration management platform called Desired State Configuration (DSC), which admins can use to set a specific configuration for a server. After the admin defines the server settings, PowerShell ensures the target nodes retain that desired state. DSC has two modes of operation: push mode and pull mode.
In push mode, a server sends notifications to the nodes. It's a one-way communication, where the admin sends notifications from a workstation. Setup costs are less because management runs from a device, but a notification can get lost if the device isn't connected to the network.
d3342ee215