Friday, January 24, 2014

Installing Citrix Provisioning Services Agent during ConfigMgr OSD deployment

The PVS Agent on a VM is necessary to create the vDisk in Citrix PVS. In this small post I describe the steps to take in order to get this successfully deployed during a ConfigMgr OSD TS.

 Create a folder containing the following information. Also check the correct processor architecture (x86/x64). The the PVS_Device.exe (or PVS_Device_x64.exe) is copied from the PVS media/ISO.
The .sys files are copied from a machine where the PVS agent is already installed on the following location: c:\Program Files\Citrix\Provisioning Services\drivers
The install.cmd executes and logs the following:

 set currentdir=%~dp0

 "%currentdir%PVS_Device.exe" /S /v/qn" ALLUSERS=TRUE REBOOT=SUPPRESS /l* %WINDIR%\Temp\CitrixPVSDeviceTarget.log"

 copy "%currentdir%CFsDep2.sys" %Windir%\System32\Drivers /y
copy "%currentdir%bnistack6.sys" %Windir%\System32\Drivers /y
copy "%currentdir%CNicTeam.sys" %Windir%\System32\Drivers /y
copy "%currentdir%CVhdMp.sys" %Windir%\System32\Drivers /y
Hope this helps some of you.

 Cheers, Niels
Posted by at
Labels: , , , , ,

3 comments:

  1. ChrisApril 16, 2014 at 5:56 AM

    Hi Niels,

    I am installing Provision Services Agent as described in your blog. When installation completes the installation triggers a reboot in the SCCM 2012 Tasksequence. Do you know how to work around this issue?
    Thanks!
    Chris

    ReplyDelete
  2. nielsvdijkApril 16, 2014 at 6:00 AM

    Hi Chris, I think you probably have to change REBOOT=SUPPRESS into REBOOT=REALLYSUPPRESS, so no automatic will occur at all.

    See also: http://msdn.microsoft.com/en-us/library/aa371101(v=vs.85).aspx

    Kind regards, Niels

    ReplyDelete
  3. ChrisApril 16, 2014 at 6:19 AM

    Thanks for you reply. I tried that and no succes. The tasksequence is getting exit code 0 so no reboot should occur. But checking the event viewer on the master vm the following is logged:
    Type of System Restart: 2. Reason for Restart: 4.

    This is something Installshield is returning to the OS and I cannot work around it.

    ReplyDelete

Subscribe to: Post Comments (Atom)