anyweb

look for the ccmsetup.log, it probably logs the error, attach it here

also, take a look at the CM12 BitLocker Frontend HTA, it has way many more things than you need in the task sequence and associated scripts, however it also deals with auto computer naming and it might be worth your while taking a look at it CM12 in a Lab - The CM12 BitLocker FrontEnd HTA

have a read of this old post, it should help you with your task in Configuration Manager at least, if you are using MDT its as easy as editing your customsettings.ini as described here.

sure thing http://www.windows-noob.com/forums/index.php?/topic/8846-how-can-i-pause-a-task-sequence-in-system-center-2012-configuration-manager/ from the index here http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-step-by-step-guides/

are you using configuration manager or not ?

yes you can deploy as many operating systems as the version of MDT you are using will support, speaking of which, XP is no longer supported by Microsoft.

hi there, i've made the change

glad you got it sorted

simply monitor the smsts.log and review the success or failure of the step setting the variable, also check the dumpvars step, it allows you to view variables that are set in winpe. to do all this, use the pause functionality built into the task sequence

did you edit the hta/javascript backend too ? what happens when you select an ou, did you confirm that it's set before the task sequence starts

below is the updated script which now includes a function to drop the network share drive letter if not needed/used ' windows-noob.com (c) niall@windows-noob.com 2014/4/14. ' This script allows you to selectively run a hidden prestart command based on previous actions. ' In addition, it will list all DeploymentId's found in a file called DeploymentIDs.txt located on a UNC share ' see http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-guides/ for details ' updated 2015-1-8 to add network share disconnect functionality ' Option Explicit DIM fso, WshNetwork, strUser, strPassword, clDrives, i, objFileToRead, strFileText Set fso = CreateObject("Scripting.FileSystemObject") Set WshNetwork = WScript.CreateObject("WScript.Network") strUser = "HiddenList" strPassword = "Password123" 'Map network drive WshNetwork.MapNetworkDrive "Z:", "\\192.168.1.2\hidden$", , strUser, strPassword 'Check if Devel Mode was selected If (fso.FileExists("x:\hidden.txt")) Then 'WScript.Echo("hidden.txt file exists, devel mode selected!") ' Now check to see if DeploymentIDs.txt file exists, this file is used so that we can display what deployment ID's are available in the prestart prompt If (fso.FileExists("z:\DeploymentIDs.txt")) Then 'Found the DeploymentIDs.txt file, read it's contents into a variable Set objFileToRead = CreateObject("Scripting.FileSystemObject").OpenTextFile("z:\DeploymentIDs.txt",1) strFileText = objFileToRead.ReadAll() 'InputBox ("The following hidden DeploymentID's are available. Please enter the Task Sequence Deployment ID:-" & vbCrLf & vbCrLf & strFileText) objFileToRead.Close Set objFileToRead = Nothing 'WScript.Quit() else 'msgbox "could not find DeploymentIDs.txt, please select manually" End If ' Devel mode was selected so display the Prestart prompt Dim env set env = CreateObject("Microsoft.SMS.TSEnvironment") env("SMSTSPreferredAdvertID") = InputBox ("The following hidden DeploymentID's are available." & vbCrLf & vbCrLf & strFileText & vbCrLf & vbCrLf & "Please enter the Task Sequence Deployment ID eg: P0120038 and click [OK] or click [Cancel] to continue.") 'MsgBox "The following Task Sequence Advertisement ID will be selected: " & env("SMSTSPreferredAdvertID") Disconnect() Else 'WScript.Echo("The hidden.txt File does not exist so will not change SMSTSPreferredAdvertID!") Disconnect() End If Function Disconnect() 'Disconnect ALL mapped drives Set clDrives = WshNetwork.EnumNetworkDrives For i = 0 to clDrives.Count -1 Step 2 WSHNetwork.RemoveNetworkDrive clDrives.Item(i), True, True Next End Function WScript.Quit()

based on your log above it doesnt understand the cmdlets Set-ADComputer when you run scripts in the task sequence they are running as System,. you should test manually running the script using psexec as system as described here basically psexec –s –i. http://blogs.technet.com/b/askds/archive/2008/10/22/getting-a-cmd-prompt-as-system-in-windows-vista-and-windows-server-2008.aspx http://windowsitpro.com/systems-management/psexec lastly, what you are trying to do must happen after the “Setup Windows & ConfigMgr” step, so that the computer is restarted after it is joined to the domain. The account which executes the script must have permissions in the AD to set the AD Description, Jorgen blogged about this using a vbs here

Microsoft's head of Windows Insider program, Gabriel Aul, has confirmed that Windows 10 will require a fresh install on Windows devices older than Windows 7. Revealed in a reply from his Twitter account, Aul wrote that there won't be any full upgrade paths as these will be solely available for Windows 7 and Windows 8.1 users. It makes sense given that some of them might be on older filesystems (e.g. FAT32). That's also assuming that Windows 10 will run on these systems, which although they may have enough resources (RAM/CPU) to power Microsoft's newest OS, may well run into compatibility issues with legacy components/peripherals (rather than software). Upgrade pathThat said, you can upgrade Windows XP to Windows 10 (Technical Preview) and still keep some (if not all) of your applications and settings in place. You will need to adhere to three rules (same bit and language versions) and have access to older Windows ISOs. Microsoft is set to reveal more details about Windows 10 at an event scheduled on January 21 at its campus in Redmond. There's even talk of an updated version of Office for Mobile being announced there. via Techradar > http://www.techradar.com/us/news/software/operating-systems/windows-7-and-8-1-pcs-will-get-direct-upgrade-to-windows-10-1278884?src=windows-noob.com

first tip would be what is logged in your smsts.log for the install software step, can you include that here ?

no it does a special format called a WIPE where it removes everything on the hard drive except the data you want to save (via custom XML rules), that data is then saved in a special folder (statestore) and the task sequence then installs Windows on on the wiped drive, when done it restores the files that were hard linked back to their original place here's an example custom xml file for doing just that http://www.niallbrady.com/2012/08/16/migrate-me-to-windows-8/

didn't you see this ? http://www.windows-noob.com/forums/index.php?/topic/6353-using-system-center-2012-configuration-manager-part-7-build-and-capture-windows-7-x64-sp1/

have you seen this yet ? 100 guides for Configuration Manager 2012 and plenty for R2 http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-step-by-step-guides/ here's one for installing R2 itself CM12 in a Lab - How can I install System Center 2012 R2 Configuration Manager ?

the guides below should give you some ideas CM12 in a Lab - How can I add a PXE enabled Distribution Point on Server 2008 X86 for System Center 2012 Configuration Manager ? CM12 in a Lab - How can I setup a Distribution Point on a Windows 7 PC in Configuration Manager 2012 ?

it's possible but would have to be done as part of your deploy task sequence simply recreate the winre area in the recovery partition by copying the winre.wim file from the c:\windows\system32\Recovery folder... to accomplish this do: set recovery partition letter in diskpart (for example Q) Robocopy.exe C:\Windows\System32\Recovery\ Q:\Recovery\WindowsRE\ Winre.wim /copyall /dcopy:t reagentc /setreimage /path Q:\Recovery\WindowsRE reagentc /enable go back in disk part and remove the drive letter set before then confirm it works with: reagentc /info in addition to the above you'll need to store your custom.wim file (the osd image) handy

can you please explain what you did to solve it to help others in the same situation in the future ? cheers niall

nope it's missing the step, it only showed the parsing Enabling BitLocker step, that isn't actually the step running, either increase your logging capability or find the correct log, see this post for how to do that.

can you attach the smsts*.log files so we can see if it has actually logged the Enable BitLocker step and determine it's success (or failure)

i've not tried it but i'm sure it's doable, i've also not heard of anyone doing it so yes perhaps you should suggest a standard refresh as I've explained in the post below (which retains all data but reinstalls the os) CM12 in a Lab - How can I reinstall BitLockered UEFI computers using network boot and System Center 2012 R2 Configuration Manager ?

well it's telling you it can't find the Install.WIM file for Windows 8.1, look at the ridiculous long file name though, that's obviously not right, look at step 3 above and read it carefully, it should resolve your problem, let me know ok ?

hi and welcome to the forums !