If you're writing a script that takes parameters with the "param" statement/feature, don't declare any variables before param. It will throw some weird errors! You can put variables in the Begin scriptblock instead.
Let's say you need to add a new user to all the Active Directory groups of an existing user. It would be painstaking and error-prone to compare group memberships in the AD Users & Computers snap-in. But don't despair: There is an easier way!
First, install the free ActiveRoles Management Shell module for PowerShell from Quest if you don't already have it. Trust me, you'll wonder how you managed Active Directory without it!
Second, run a command like this in PowerShell:
When working with group policies, if you get this error, make sure that you are not setting up Security Filtering for let's say, "Authenticated Users" (which is the default for a new GPO) when you're trying to set computer-level group policy settings.
User Policy update has completed successfully.
Computer policy could not be updated successfully. The following errors were encountered:
I just transferred this site (pixelchef.net) to www.nearlyfreespeech.NET webhosting!
I ran into a lot of trouble with PHP Safe_mode restrictions. I tried everything I could find on the web to no avail. So I caved in and set the site mode to PHP Flex, which does away with Safe_mode, and everything is fine now. It sounds like the site is less secure, but I don't know what else to do. And I found in the official PHP docs, Safe_mode has been depreciated and should not be relied on anymore. So maybe it doesn't really matter.
Here's a quick one-liner to retreive the status of a Windows service on a remote computer using Powershell. You don't need PowerShell remoting for this to work because it uses WMI.
This example uses the SNMP service, so just replace that text with the particular service you're looking for. Also replace remotecomputer with the name of the computer you are querying. If you remove '-computername remotecomputer' you will query your local computer.
When you deploy Office 2010, users are prompted to make changes to "Use Recommended Settings", "Install Updates Only", or "Don't make changes" when they open Office 2010 for the first time. These relate to software updates for Microsoft Office, as well as the customer feedback program and other miscellaneous things.