Skip to main content

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)

· Microsoft Virtual Server 2005 R2 or above.

· Microsoft Virtual Server 2005 R2 x64 SP1 or above.

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.

clip_image002

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

Popular posts from this blog

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.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .