Manually Deploy SCVVM Agent

The System Center Virtual Machine Manager (SCVMM) agent allows a SCVMM server to manage the virtual machines on that host. When you use the SCVMM console to add a host, the SCVMM agent software is installed on that host. If the host is in a perimeter network or not on the domain, you need to add the agent software manually before joining it to a VMM server.

Before you install the SCVMM agent, your host must meet the following requirements. (List below provided by Microsoft)

An operating system supported by VMM.
For more information about operating systems supported by VMM, see Supported Operating Systems for Virtual Machine Manager.
One of the following versions of Microsoft Virtual Server 2005:

· Microsoft Virtual Server 2005 R2 or above.

· Microsoft Virtual Server 2005 R2 x64 SP1 or above.

Windows Remote Management (WinRM).
You must install this software from the following site:http://go.microsoft.com/fwlink/?LinkId=84599.

If you are using Windows Server 2008, you are good to go. These instructions are valid for installing SC VMM agent on a host in a trusted domain.

Double click Setup.exe from the installation media of SCVMM

Click Local Agent.

Click Next.

Check I accept the terms of this agreement and click Next.

Choose the location of where you want the agent to install to and click Next.

On the Configuration Settings page, you must configure the agent to use the same ports as the SC VMM server. Click Next.

If this host is on a perimeter network, you need to configure the authentication between the host and the VMM server. You can do this via a security file or a certificate. Click Next.

Click Install.

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog