I have various fully working online and offline Windows server builds, so generally do not have any issues with deployments, but we have recently gotten a requirement for offline builds with applications integrated.
The applications are large install like Citrix, which have needs for multiple reboots and passing of variables.
I am able to deploy the OS and Citrix deployment as 2 separate jobs, when online and the SCCM host is accessible. What I want to do is include the Citrix job in the OSD job and create 'offline media'
I can compile the offline media OK - and it appears to run OK - but it seems that when the application install steps (executed as 'Run Command Line') run, they do not run the same as part of an OS deployment job, as they do when run as part of an isolated package install job.
The scripts run using Powershell (Yes execution policy etc is all OK and the scripts are called from command lines which work when used as a stand alone job)
What is the big difference between an OSD job and a Deploy Package job, that makes the environment behave differently - and how do i I get around it?
Can I make the Citrix install run after the OSD, but still part of the same task sequence?
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
I have various fully working online and offline Windows server builds, so generally do not have any issues with deployments, but we have recently gotten a requirement for offline builds with applications integrated.
The applications are large install like Citrix, which have needs for multiple reboots and passing of variables.
I am able to deploy the OS and Citrix deployment as 2 separate jobs, when online and the SCCM host is accessible. What I want to do is include the Citrix job in the OSD job and create 'offline media'
I can compile the offline media OK - and it appears to run OK - but it seems that when the application install steps (executed as 'Run Command Line') run, they do not run the same as part of an OS deployment job, as they do when run as part of an isolated package install job.
The scripts run using Powershell (Yes execution policy etc is all OK and the scripts are called from command lines which work when used as a stand alone job)
What is the big difference between an OSD job and a Deploy Package job, that makes the environment behave differently - and how do i I get around it?
Can I make the Citrix install run after the OSD, but still part of the same task sequence?
Thanks
Share this post
Link to post
Share on other sites