Last week I promised a post on enabling PowerShell Remoting when we discussed automating service account password updates . So, let’s break down the two methods. First we have the manual method. For this, all you need to do is remote desktop into the machine that you want to enable PowerShell Remoting on and execute the Enable-PSRemoting cmdlet in a PowerShell console window, running as administrator. So that was easy but very ineffective when managing a large number of servers. Which brings us to the Group Policy method. With Group Policy you can have all your servers inherit the necessary configurations when they process a Group Policy update. Fortunately for us, there have already been a couple of great procedures written on this. Check out this procedure, from blog.powershell.no, which covers Windows 7 and later or Windows Server 2008 R2 and later . Check out this procedure, from Jfrmilner’s Tech Blog, which covers Windows 2003 and Windows Xp . Written by Derik Hammer of SQL Hammer Derik is a data professional focusing on Microsoft SQL Server. His passion focuses around high-availability , disaster recovery , continuous integration, and automated maintenance. his experience has spanned long-term database administration, consulting, and entrepreneurial ventures. Derik gives the SQL community credit for plugging the gaps in his knowledge when he was a junior DBA and, now that his skills have matured, started SQLHammer.com as one small way to give back and continue the cycle of shared learning. Derik is the owner and lead author of SQL Hammer, a Microsoft SQL Server resource . For more information, visit http://www.sqlhammer.com . Follow Derik on Twitter for SQL tips and chat
↧