Hoping someone can assist with this issue. We are creating a Windows Server 2008 R2 and Windows Server 2012 deployment solution for a customer and have two nearly identical Task Sequences where one is used to deploy Server 2008 R2 and the other deploys
Server 2012 RTM.
We are running a PowerShell customizations script as part of each Task Sequence. Running the script outside of the TS works fine on each OS platform but when running the script within the Task Sequence, the script executes successfully and makes all of
the changes it is supposed to, but on Windows Server 2012 it then causes then next step in the Task Sequence to fail every time. In the Windows Server 2008 R2 sequence everything runs OK and the deployment returns success on the Summary screen but on
Server 2012 it shows an error on the item after the PowerShell script and stops the TS.
On the Server 2012 system, looking in the %WinDir%\Temp\DeploymentLogs folder the log for the PowerShell script returns exit code 0 (Success!). Checking the customizations that the script is supposed to do shows they are all there. So the script
ran, made all the changes and reported success, but then the next item in the TS fails.
Right now we run the customizations script near the end of the sequence and it runs, followed by the Symantec EndPoint installation (which fails with the proverbial 1603). We've moved Symantec to be before the PS script and it runs fine, but then the
PS script runs and the "Restore Groups" task after it fails. If we disable the PS Script step the entire TS runs successfully.
What could be different on Server 2012 for this step?
Edited byJeffLe73Wednesday, December 12, 2012 2:57 PM
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.