You are browsing the archive for Vmware.

Configmgr 2012 : How to create custom boot images that will support #VMware’s native VMXnet3 NIC

8:46 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2012, ConfigMgr 2012 SP1, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, SCCM 2012, SCCM 2012 SP1, sccm2007, Vmware by Kenny Buntinx [MVP]

 

Though VMware Tools does not support the WAIK or ADK’s WINPE 3.1 environment, you can take advantage of specific VMware Tools drivers, such as vmxnet3, and pvscsi by creating a customized Configmgr 2007/2012 Boot Image .

To create a customized Configmgr 2007/2012 Boot Image :

  • On your Primary site server Click Start > All Programs > Microsoft Windows AIK > Windows PE Tools Command Prompt to open the Windows PE Tools command prompt.
  • Run this command to create a Windows PE build environment in the WinPE folder.
      • for a 32bit boot wim – copype x86 C:\winpe-x86
      • for a 64bit boot wim – copype amd64 C:\winpe-amd64
  • Install VMware Tools on Windows 2008 and copy the entire contents of the C:\Program Files\VMWare\VMWare Tools\Drivers\pvscsi and vmxnet3 folders to a C:\VMDrivers folders on the virtual machine.
  • From the Windows PE command prompt (<Drive>:\winpe-x86), run this command to mount winpe.wim to the mount folder:
    dism /mount-Wim /wimfile:<drive>:\winpe.wim 1 /mountdir:<drive>:\WinPE_tmp
  • Run this command at the Windows PE Tools command prompt to copy the vmxnet, vmxnet3 (enhanced), and pvsci drivers:
    winpe.wim: dism /image:<drive>:\WinPE_tmp /Add-Driver /driver:c:\VMDrivers /recurse
  • Run this command to save the changes to winpe.wim:
    dism /unmount-Wim /Mountdir:<drive>:\WinPE_tmp /commit

Import your custom bootimages in Configmgr 2007/2012 and distribute them to your DP . Your done !

Hope it Helps ,

Kenny Buntinx

SCVMM 2012 : Adding ESX 4.1(i) hosts will fail when using root account

10:23 am in SCVMM, SCVMM 2012, System Center, Vmware by Kenny Buntinx [MVP]

Maybe this is a very small blog post , but I think it could help some people out Smile

When you want to add your physical ESX 4.1 hosts with the root account and it does not succeed ( getting an access denied ) , it means that your hosts are in lockdown mode !

Switching off “Lockdown mode” gives you back the possibility to add your hosts with your root account.

Hope it Helps ,

Kenny Buntinx

Opalis 6.3 : Building a VMware/SCCM Opalis provisioning workflow

7:54 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Deployment, Installation, Opalis, Opalis 6.3, Operating System Deployment, powershell, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, Virtual machine, Vmware by Kenny Buntinx [MVP]

Recently we did a customer private cloud project where we used all the system center tooling ( http://www.microsoft.com/systemcenter/en/us/default.aspx) , except for the hypervisor layer , which was VMware .

One of the scenarios that the customer had in mind , was to provision all there virtual servers with SCCM and we had to use Opalis to become the glue between VMware – BMC Remedy and System Center. In the first step of the project we didn’t use the Change request mechanism from BMC Remedy yet. Special thanks to my colleague Gunther Dewit for helping me out on this one .

**** Disclaimer **** – This is a very basic workflow – we will post improvements as we go along – it is for helping people moving forward **** Disclaimer ****

The workflow itself

image

Delivering input

image

The first step in creating a workflow is doing a custom start where we could input some necessary variables . The Custom Start Activity is used to create a generic starting point for Workflows. By adding parameters to the Custom Start Activity it can consume external data which can be passed to downstream Workflow Activities.

image

These are the parameters the workflow needs in further steps.  All the rest of the information that is residing in the data bus of Opalis  .

This input is required, without it, the workflow won’t start. A popup will be presented when starting the workflow.

Now that we have all the necessary input required, we can continue with the creation of the virtual machine. In order to create a virtual machine, we need to provide some parameters, some of them will come from the Custom start step, others will have to be adapted per workflow.

 

Creating the virtual machine

image

image

These are the required parameters.

  • Name: This is the name that will be given to the virtual machine, we will get it from the Custom Start  where we filled in a name.
  • Datastore: This is the datastore that will host the virtual machine disk, we will get it from the Custom Start  where we filled in the datastore.
  • DiskMB: Since it was decided to have a fixed disk with a size of 100GB, we filled it in directly instead of asking it in the first step.
  • DiskStorageFormat: This is the thick or thin format, thin was decided as the default format.
  • MemoryMB: This is the amount of memory that will be given to the virtual machine, we will get it from the Custom Start where we filled in an amount of memory.
  • NumCPU: This is the number of CPU’s that will be given to the virtual machine, we will get it from the Custom Start where we filled in the number of CPU’s we need.
  • CD: It was decided that all VM’s will have a cd drive so we set this to true.
  • VMSwapFilePolicy: This will set the swapfile policy the states where the swapfile will be saved, it was decided to do this in the VM itself.
  • VMHost: This is the physical host where the VM will be hosted, this integration pack cannot provision on cluster yet so you need to choose a physical host.
  • GuestID: This is the OS version that will be installed on the VM.
  • Folder: This is the foldername where the VM will be installed as shown in the ESX console.

You can add more details trough the “optional properties” button. If all goes well, the workflow has created the virtual machine now.

Now we need to change some things on the virtual machine.

 

Getting the network adapter settings from the created virtual machine

image

First we need to change the network settings. The VM name, we get from the Custom Start , since this is a read action, no further settings are needed.

Alternatively, you can specify some filters to narrow the data that you receive back.

Alternatively, you can specify some filters to narrow the data that you receive back.

image

Now we will delete all the network connection that VMware made by default because they are useless to us.

 

Removing the network adapters from the virtual machine

image

image

The Network Adapter name is data that we got back from the read action above and the VM name is still the name entered at the Custom Start .

This will remove all network adapters from the VM, alternatively, you can specify filters if you only want to delete a specific adapter.

 

Adding the production network adapter to the virtual machine

image

Now we need to add a network adapter to the VM. The VM name is still the name we entered at the Custom Start .

image

The NetworkName is the name of the network that you want your network adapter connecting to.

The StartConnected specifies if it will be connected to the network or only added without being connected.

The Type is e1000 as this is the only VMware adapter SCCM can work with.

Now we do another step to get the properties from the newly created adapter so we can use the information to input the computer into SCCM.

 

Getting the production network adapter settings from the virtual machine

image

image

Now that we collected the necessary information for SCCM, we can import the computer into SCCM.

This is done by a powershell script that needs to input parameters, the name and the MAC address.

 

Adding the computer to SCCM

image

Now that the computer is known is SCCM, we need to add it to the collection that has the OSD advertised to it.

image

The is done by the following step.

 

Adding the computer to an SCCM collection

image

In the collection field, you can enter 2 things, either the name of the collection or the ID of the collection. What you enter must match the collection value type. If you enter an ID as shown here, the value type must be ID as well. The same is true for the computer where we use the name from the Custom Start step so the value type is name in this case.

image

Now that the VM is created and provisioned in SCCM, we are ready to deploy the operating system on it.

So let’s power on the VM.

 

Powering on the virtual machine

image

The only thing you need to power on a VM is the name and we still get the from the first step.

image

Now that the VM is booting up, SCCM can start the task sequence to deploy an operating system on the VM.

Meanwhile, we will check the progress in Opalis.

 

Getting the virtual machine deployment status

image

The advertisement ID is the ID as it is known in SCCM and the computer name is still the name as we specified in the first step.

image

Looping the task

Now since the OSD deployment takes some time to complete, we will let the step loop until it gets a result back from SCCM.

image

image

It will recheck every 300 second and will do this 8 times or when it gets back from SCCM that the deployment was successful in order not keep the loop while the deployment was finished faster then in 8 loops.

 

Getting the deployment result

image

Now we need to output the result to any medium you want (logfile, mail, …), I do an output to a text file as an example.

Conditional progress

Now how does Opalis know when to write to which log file?

This can be regulated by double clicking on the arrows. This is the arrow toward the success file.

image

As you can see, it will only follow this arrow when SCCM outputs a succeeded message for the advertisement. If not, it will take the other path towards the failed log file.

 

So , It is not so easy to get it all together , but if I may give a great tip: ” Write down all steps of your manual flow  and then try to translate them into an opalis workflow “

 

Hope it Helps ,

Kenny Buntinx

SCCM : Deploying Windows 7 on a VMware ESX environment ( howto )

3:13 pm in ConfigMgr, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, Drivers, Installation, OSD, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 SP2, sccm2007, script, Vmware, Windows 7 by Kenny Buntinx [MVP]

Hi ,

Did you ever wanted to build a reference image of your physical workstations onto your VMware ESX environment ( yes , some customers have a firm grip on vmware …) so that people could play around ?

In my previous post , I explained already on how to perform this for Vmware workstation and the process isn’t that much different. see

http://scug.be/blogs/sccm/archive/2009/04/20/sccm2007-osd-customising-your-task-sequence-for-building-a-client-os-on-your-vmware-workstation-6-0-or-later.aspx

Well , I have a lot of customers demanding for this scenario as well and here is how you get started :

Prerequisite: Make sure that you have at least ESX 3.5 update 5 !

Step 1 : Download the drivers of the “Intel PRO Network adapter” from the Intel site ( www.intel.com)

Step 2 : Copy the drivers to a folder from the extracted VMware tools on your SCCM Primary server & import those drivers into the driver database . Make sure to assign a category to it .It could be perfectly VMware like in the example below.

 image

Step 3 : When done , alter your Windows 7 deployment task sequence and add a “auto apply driver step”

Step 4 : Limit the driver scope to the Vmware category earlier defined as shown below.When done , click OK.

image

Step 5 : Make sure that your settings in your VMware are representing the following settings.

For Windows 7 32 bit :

TRUVO-0020

For Windows 7 64 bit :

TRUVO-0021

Step 6 : Once done , you boot your machine in PXE and start staging . That’s it . However do not forget to add your VMWARE Tools into your tasksequence .

TRUVO-0019

Hope it Helps ,

Kenny Buntinx

SCCM : ESX VMWare Vsphere 4 Tools Silent Install/Upgrade in an Windows 2008 R2 OSD Task Sequence ANSWER !

3:29 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 SP2, sccm2007, Vmware by Kenny Buntinx [MVP]

We struggled with this for a long time, but we finally found a way to make it work. We could deploy the tools manually with no issue, but trying to automate it was a complete nightmare.

Basically, the problem turned out to be that trying to use setup.exe from VMware to do an automated Install is effectively impossible.

The supported solution from Wmware  that we initially found was to use setup.exe. The command was: setup.exe /s /v"/qn"

The only caveat to be aware of is that if you’re scripting the process in a task sequence for example , that the command will execute, spawn the install/upgrade process, and then immediately terminate. Hence, your task sequence or whatever will think that the command has finished even though the upgrade has just started to run in the background. We normally suppress all reboots in our packages and then decide when to boot via the Task sequence, but in this case that was not possible. Even with the reboot=Suppress option to the install the VMware tools would finish executing with instantly rebooting and failing your Task Sequence.

When we’re installing the tools, we use msiexec because it doesn’t have the "terminates instantly" problem that you get with setup.exe and is therefore easier to deal with in your task sequence.

That command is : msiexec.exe /i VMwareToolsx64.msi /QN ADDLOCAL=ALL REBOOT=ReallySuppress ( make sure to rename your msi file and remove the space in between !)

Using that method, we successfully Installed the VMware tools in out  Windows 2008 R2 x64 task sequence .

 

Hope it helps

Kenny Buntinx.

How to monitor the hardware of an HP server when running VMWARE ESX in SCOM R2

12:25 pm in MOM, Operations Manager 2007, Opsmgr 2007, SCOM 2007, Virtual machine, Vmware by Kenny Buntinx [MVP]

I ran into a situation that a customer did not want to pay for an expensive management pack to monitor their ESX server Hardware . They all ran on HP Proliant hardware. Here is a small tutorial on how to integrate & configuring the Insight Manager Agents for VMware ESX Servers and let them report into System center Operations Manager 2007 R2

  1. Go to the HP website and search for HP Insight Manager Agents for VMware ESX Server 8.2.0
  2. Download the Agents
  3. Open WinSCP and upload the .tar file you just downloaded to a folder
  4. Log into putty with your root account
  5. Issue the following command to unzip the contents: tar -zxvf hpmgmt-8.2.0-vmware.tgz.
  6. Stop the pegasus services : “Service pagasus stop”
  7. Run “hpmgmt820preinstall.sh –install”
  8. Reboot
  9. Stop the pegasus services : “Service pagasus stop”
  10. Run “hpmgmt820install.sh – install”
  11. Follow the wizard, when asked for the public string enter (if you use this string) public 2 times (it will not be visible), and be sure to have the HP SIM server’s IP or FQDN. Always answer Y when asked to activate the port 2381 (HPMHP) & the Snmpd deamon.
  12. After the config you need to start the pegasus services : “Service pagasus start”
  13. To check if the configuration has succeeded, log in to the HP System Homepage https://<esx server>:2381/. You should see the servername on the right side.Log in with Root
  14. Check your snmpd.conf  at /etc/snmp/snmpd.conf . It should look like this :

———————————————————————————–

# Following entries were added by HP Insight Management Agents

dlmod cmaX /usr/lib/libcmaX.so

rwcommunity public 127.0.0.1

rocommunity public 127.0.0.1

rwcommunity  public <The FQDN name of your RMS server>

rocommunity public <The FQDN name of your RMS server>

trapcommunity public

trapsink <The FQDN name of your RMS server> public

syscontact root@localhost (edit snmpd.conf)

syslocation DATACENTER

# ———————- END ——————–

# Sample snmpd.conf containing VMware MIB module entries.

# This is a simple snmpd.conf that may help you test SNMP.

# It is not recommended for production use. Consult the

# snmpd.conf(5) man pages to set up a secure installation.

# VMware MIB modules. To enable/disable VMware MIB items

# add/remove the following entries.

dlmod SNMPESX            /usr/lib/vmware/snmp/libSNMPESX.so

———————————————————————————–

You are done on the ESX Level ! Now we move on to the SCOM R2 Level .

It is relatively simple to monitor the hardware status of your ProLiant servers with Operations Manager. HP  has a free management pack (HP ProLiant Management Pack for System Center Operations Manager 2007), that discovers and monitors them. However if your ProLiant servers happen to have a different OS than Windows installed, it will not not work without a hassle.

I was looking for a way to include the hardware status of our HP servers that ran VMware ESX 3.5 update 4  into OpsMgr. HP does provide a specifically adapted Management Agent for ESX (HP Management Agents for VMware ESX Server as described above ). That allows accessing hardware information about the server using SNMP queries.

On Raphael Burri’s blog you will find a custom written MP that will collaborate with the HP Management pack for Windows and let you monitor your HP hardware . Many thanks to him !!!!

  1. Download the custom made management pack from Raphael Burri on http://rburri.wordpress.com/2008/06/03/snmp-only-hp-proliant-hardware-management-pack/
  2. Download the official HP Management pack for HP Proliant Servers
  3. Install the SNMP stack on your RMS server
  4. Import the both Management packs in your RMS
  5. Configure the SNMP stack of the non-windows ProLiants to allow access from the OpsMgr server or gateway that is going to act as SNMP proxy.
  6. Discover the ProLiant servers as SNMP Network Devices
  7. You are done . Create your own views and rules as you want .

 

Hope it Helps ,

Kenny Buntinx

SCCM2007 OSD : Customising your Task Sequence for Building a Client OS on your VMWare Workstation 6.0 or later

10:04 am in ConfigMgr, ConfigMgr 2007, OSD, sccm, SCCM 2007, Virtual machine, Vmware by Kenny Buntinx [MVP]

Hi ,

Did you ever wanted to build a reference image of your physical workstations onto your VMware Workstation so that people could play around ?

Well , I have a lot of customers demanding for this scenario and here is how you get started :

Step 1 : Download the drivers of the “Intel PRO Network adapter” from the Intel site ( www.intel.com)

Step 2 : Install the VMware workstation 6.5 software on a client . Navigate to the following folder “c:\Program Files\VMWare\Vmware Workstation\wmware_drivers.cab” , extract those drivers to a folder .

Step 3 : Copy the drivers to a folder on your SCCM Primary server & import those drivers into the driver database . Make sure to also create a Driver Package & replicate it to the selected DP’s

SNAG-0024

Step 4 : Obtain the VMware Client Tools and create a package into your SCCM server . Create a program with the following line “ Msiexec /I “client tools.msi” /QN

Step 5 : Edit your task sequence and add the earlier created driver package :

SNAG-0018

 

 

 

 

 

 

 

As you can see , I have multiple hardware’s included .To sort them out , I use wmi queries and that is explained below .

Step 6 : In the properties pane , select your correct driver package and select “do unattended installation if unsigned drivers …….”

SNAG-0020

Step 7 : Go to the options tab and create a wmi query that will only apply/install the drivers when it is a VMware .As shown in the example below.

SNAG-0021

Step 8 : Create a subsection to install specific HW driver software . In this case the VMware client tools .

SNAG-0019

Step 9 : Select you earlier created package

SNAG-0022

Step 10 : In the options tab , you repeat your wmi query as shown above :

SNAG-0023 

Step 11 : You think you are done ? Well on the server side you are , but on the client side you must adapt some client settings to get it working .

Step 12 : Adapting the Virtual network drivers to support the WinPe SCCM enviroment.

Step 13 : After your Virtual machine has been created , the network card is not supported for the SCCM PXE boot . You will need to alter manually the *. Vmx file with notepad and add a line to it.

MAKE SURE YOU CLOSE YOUR VMWARE WORKSTATION APPLICATION BEFORE UPDATING THE FILE! OTHERWISE YOUR CHANGES ARE NOT REFLECTED!

Open the *.VMX file where your VM is located and add the following line :

Ethernet0.virtualDev = “e1000”

image

Save the file and exit the application.

Step 14 : Record your Mac adress and importing it into SCCM to deploy your VMWARE image .

 

Hope it helps ,

 

Kenny Buntinx