Hi all
Does anyone had the pleasure of installing Sage Act 10 Prem + Act update + Act hotfix using MDT? Our standard install of act requires for me to first run the installer, then the update and then the hotfix. I am not actually sure if the update and or the hotfix got silent installers. if not, do i have any other options with MDT? thinking of a repackager, but never had much luck with those.
Regards
ronnie.jorgensen systems engineer
My blog
Hello
I have a couple of problems I was hoping you could help with.
Q1. How do I set the Keyboard Input to be UK from this prompt:
Its set to US by default.
Q2. How do I set the properies in here to be automatic?
They dont seem to be automatic given my .ini & bootstrap.
Q3. It wont join the domain, just fails after three attempts. What am I doing wrong?
CustomSettings.ini:
[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipBitLocker=YES
OrgName=Deployed by XXXXXX
SkipTimeZone=Yes
TimeZone=085
TimeZoneName=GMT Standard Time
SkipUserData=YES
UserDataLocation=None
SkipLocaleSelection=YES
KeyboardLocalePE=0809:00000809
UserLocale=en-GB
UILanguage=en-GB
JoinDomain=home.network
DomainAdmin=home\administrator
DomainAdminDomain=home.network
DomainAdminPassword=12345
AreaCode=01332
CountryCode=044
Bootstrap.ini
[Default]
DeployRoot=\\SERVER2008\DeploymentShare$
KeyboardLocalePE=0809:00000809
UserDomain=home.network
UserID=administrator
UserPassword=XXXXX
ALSO: This is for a KMS environment, once machines are imaged & apps installed will I need to sysprep them so the CIDs will be unique for VAMT or do I have antoher step to do?
THANK YOU in advance to the experts!
This is in a test environment but I need to get to the bottom of it before I roll it out. Cheers
When using MDT to deploy an OS to a completely empty disk (zero partitions) - MDT will fail to make the disk bootable, it would seem:
SMSTS.log
User did not specify local data drive TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume A:\ is not a fixed hard drive TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume D:\ is not a fixed hard drive TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume W:\ has 30643773440 bytes of free space TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume W:\ is not bootable TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume X:\ is not a fixed hard drive TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Volume Z:\ is not a fixed hard drive TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
TSM root drive = TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
We do not find an available volume to store the local data path TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Set a global environment variable _SMSTSNextInstructionPointer=47 TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Set a TS execution environment variable _SMSTSNextInstructionPointer=47 TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Set a global environment variable _SMSTSInstructionStackString=41 TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Set a TS execution environment variable _SMSTSInstructionStackString=41 TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Save the current environment block TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
pszPath[0] != L'\0', HRESULT=80070057 (c:\qfe\nts_sms_fre\sms\framework\core\ccmcore\path.cpp,58) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\environmentlib.cpp,639) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Failed to save environment to (80070057) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,842) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
SaveEnvironment(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,420) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Failed to persist execution state. Error 0x(80070057) TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
Failed to save execution state and environment to local hard disk TSManager 6/4/2013 10:44:19 PM 2144 (0x0860)
-----
However, it's showing that it is successfully making it bootable:
LTIApply.log
Event 5625 sent: The image \\SERVER\AdminDeployment$\Operating Systems\win2008r2\win2008r2.wim was applied successfully. LTIApply 6/4/2013 10:43:33 PM 0 (0x0000)
About to run command: "\\SERVER\AdminDeployment$\Tools\X64\bootsect.exe" /nt60 W: LTIApply 6/4/2013 10:43:33 PM 0 (0x0000)
Command has been started (process ID 1880) LTIApply 6/4/2013 10:43:33 PM 0 (0x0000)
Console > Target volumes will be updated with BOOTMGR compatible bootcode. LTIApply 6/4/2013 10:43:33 PM 0 (0x0000)
Console > W: (\\?\Volume{c3ed9a1f-cda5-19e2-b519-00155d546500}) LTIApply 6/4/2013 10:43:33 PM 0 (0x0000)
Console > Successfully updated NTFS filesystem bootcode. LTIApply 6/4/2013 10:43:41 PM 0 (0x0000)
Console > Bootcode was successfully updated on all targeted volumes. LTIApply 6/4/2013 10:43:41 PM 0 (0x0000)
Return code from command = 0 LTIApply 6/4/2013 10:43:41 PM 0 (0x0000)
Find the boot drive (if any) [True] [6.1.7601.18015] [False] LTIApply 6/4/2013 10:43:41 PM 0 (0x0000)
New ZTIDiskPartition : \\MININT-QSI0A4R\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-QSI0A4R\root\cimv2:Win32_LogicalDisk.DeviceID="W:" LTIApply 6/4/2013 10:43:42
PM 0 (0x0000)
-----
If I reboot and try again (now that the system has a formatted disk) - it always works. This happens 100% of the time under the following condition -If there is more than one physical disk. I can't purposely recreate this on a single disk. I'm not even touching that second disk during build, so I don't know why it would affect it. I've tried both booting from media as well as PXE - same thing each time.
Oddly, when the disk is clean to begin with, MDT chooses W: for OSDisk. When it has to clean the disk, it chooses V:.
Anyone have any ideas?
Hi all
I am reasonably new to MDT and would like to hear from others about how to handle drivers. More specifically about creating sub folders in the out of box drivers and go like Dell\Desktops\Windows 7
I am currently using DRIVERGROUP001 variable and using make and model so i have Windows 7 x64\Dell. Inc\Optiplex 7010
Since setting up my config this way i have noticed that if i go to Dell's website and download windows 7 64 bit drivers for my optiplex 7010, those drivers also contain 32 bit drivers. also i am aware of many Dell models will use the same drivers.
So i have been toying with the idea of adding everything in to bigger groups. for exampleOut-Of-Box Drivers\Dell\Desktops and then put in Windows 7 and XP drivers into here for 32 bit and 64 bit? or maybeOut-Of-Box Drivers\64 bit\Dell\Desktops.
I would very much like to hear if others are doing it this way and what their results are?
Cheers
Regards
ronnie.jorgensen systems engineer
My blog
Hi i am using MDT 2012 Update 1 with USMT 5.0 , i am getting error when trying to rebuild a Win laptop with data migration i am getting the following error
ZTI ERROR - Non-zero return code from Scanstate, RC=11
FAILURE (9707): Non-zero return code from USMT capture, rc=11
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run action: Offline User State Capture
CNAME loop detected. (Error: 000025EB; Source: Windows)
The execution of the group (Preinstall) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Offline User State Capture. Execution of task sequence failed.
CNAME loop detected. (Error: 000025EB; Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
.
I have uninstalled USMT 5.0 and installed 4.0 and updated the deployment share....
Still am getting the same error
can anyone help me in this
i have edited the Customsetting.ini as below
Settings]
I'm trying to capture a customised Windows 8 install to use as our SOE, the capture itself completes without errors but when I try to deploy the image with a Standard Client TS the deployment process pauses after a reboot and AutoLogon.
If I manually run C:\LTIBootStrap.vbs then the deployment process resumes and completes but with a failed Domain Join, if I manually join the domain before running LTIBootStrap.vbs then the deployment process is successful although start menu settings aren't
copied. (I've also noticed that the computer name remains the same as the base image even though I've specified a computer name in the wizard)
At first I thought my Task Sequence might be wrong but if I change the OS from the custom capture to standard Win 8 Pro then the deployment works perfectly.
I've done alot of searching to see if people are having similar issues and that's pointed to a possible problem with the Sysprep process when I run the capture?
The steps I've taken are as follow.
1. Install Windows 8 Pro into a VM using the Microsoft VL ISO
2. Customise Windows 8 by installing base applications, applying Windows Updates, Wallpaper, Screen Saver etc
3. Launch the capture process from an elevated command prompt 'cscript \\mdt\MDTDevelopment\Scripts\LiteTouch.wsf
4. Import the successfully captured image into MDT2012 (specifying the setup files as the clean Windows 8 OS)
5. Create a TS and edit it's Unattend.xml to change CopyProfile to true.
6. Deploy via WinPE specifying a computer name for the new machine.
This is what I've been doing with MDT2010 and Windows 7 deployments for a number of years and it's worked fantastically, has something changed in MDT2012? I've tried to find guides but haven't been able to find any that describe how to deploy a custom Win 8 image, the MDT2012 documentation also didn't help me.
Appreciate any guidance you can give.
Thanks
We have an image that was not created by me but another party, and the problem I am having now is when I deploy the image using MDT 2012 Update 1, I get the "windows activation period is over" error with the "Activate windows online now" prompt before the OS is installed, I have edited the unattend.xml file that I used to deploy the image and added the SkipRearm=0 step to the xml file along but I still get the prompt and I also noticed that the CMIDS are not changing even after I select activate. I can add the slmgr /rearm and slmgr /ato to change the CMIDS in the task sequence but I really want to get rid of the "Activate windows online " prompt. I have run out of ideas, maybe the image was sysprepped 3 times already and the activation period can not be reset anymore, I'm not sure, but we activate with a KMS server and I do not specify any license key in the XML file, when I run slmgr /rearm and then slmgr /ato it activates fine and changes the CMIDS but I just want to get rid of the prompt, Please help, I have wasted so much time trying to make this work. Thanks in advance!!
Bobby98
We have an issue with an employee who uses two different desktops in deploying Lotus Notes 8.5.3. We have both ID's pointing correctly but still fails to login with failure to find file... Any additional suggestions? Both the user security information is
the same with the one PC that is working with Lotus Notes...We are using XP as well on both of these desktops..
I am attempting to image a Lenovo W520 laptop using a Lite Touch image .iso file from a USB key that I created in MDT 2010. This image works successfully on all other Lenovo's in my environment (X220, T420, etc.). After successfully booting to the USB key& choosing my task sequence, the process fails when the OS begins to be installed & I receive the error message: "Setup was unable to create a new system partition or locate an existing system partition. See log files for more information."
To attempt to resolve, I formatted the HD & retried. Same result. Anyone else experience & resolve this issue? Thanks.
I'm trying out using MDT 2012 and WinPE 4.0, upgrading things. I've recreated things following templates in MDT 2012. I'm also using ADK and WinPE 4.0.
Issue I'm seeing is upon restarting into WinPE I see the screen showing Windows is Loading Files and the progress bar. I see the first one load through and then the second slower one load through. Once progress bar fills, it just does nothing and I'm left looking at a complete progress bar.
I was trying obviously first using VMWare ESX 5.0 with no success, subsequently tried a couple of physical machines and those had no problems. I still want to get working on ESX since that will help speed up development and testing of the rest of the stuff I need to upgrade. Tried a variety of SCSI controllers within ESX vms. I tried VMWare Workstation 9 with the mixed results as with the LSI Logic Parallel SCSI controller had success but not the others.
I of course at first tried making sure drivers were added with no change, although that still could be an issue with drivers I found to put in being incorrect.
More interestingly though is that I can of course install Windows 8 from install media just fine on these hardware, as well as if I create an ISO from the deployment share and boot to that it works just fine, so it seems to just be an issue when booting to WinPE on disk.
Any ideas are greatly appreciated. Thanks.
We are in a process of migration from XP to windows 7. As of now we are not using standard partition structure. Moving further with Windows 7 my people want to manage a standard Partition structure, say C-->50 Gb, D-->5Gb for Paging file, E-->Remaining.
As per my knowledge we can do migration without Formatting existing Hard Disk and we have done that already. But one of my Project requirement is like above. Can some one help me with this.
How to do this. I don't have much knowledge on generating Custom XML Files. :(
Thanks in advance.
Janakiram NHV
I am trying to execute MDT 2012 task sequence from local system as an offline media. There is a twist in requirement wherein users are copying offline media to USB or local drives (root of any drive) and running batch file to call LiteTouch.vbs. Since the process is independent of IT support personnel and no recommended guidelines, my deployment share must be able to run from any drive location instead of being a static path in bootstrap.ini. Present bootstrap.ini as below.
[Settings]
Priority=Default
[Default]
DeployRoot=C:\Content\Deploy
SkipBDDWelcome=YES
UserID=none
UserPassword=none
UserDomain=none
Any thoughts on setting the relative path to deployment share?
Im just trying to get a handle on what scripts/xml files are loaded/processed and in what order after winpe is loaded and before the selected task sequence starts.
This is what I have so far:
After winpe is loaded, somehow, magically, ZTIUtility.vbs is loaded to provide all the basic functions required by other scripts.
To display the first credentials screen, Credentials_ENU.xml and credentials_scripts.vbs are used to display and gather credentials.
The rest of the screens that ask questions are all controlled by DeployWiz_Definition_ENU.xml (which contains references to vbscripts).
Once the task sequence has been selected, LTItouch.vbs is run which runs the selected task sequence.
Have I missed anything really fundamental?
Thanks
We are trying to create a post installation task sequence that will do the following with mdt 2010:
- change computer name
- join domain
- install some apps
- change local password
My biggest problem so far with this idea is that the post installation task seems to ignore my autologon settings in my unattend.xml file. Its seems to have its own set up somewhere for the local account.
Essentially once I run the task and when it reboots as some stage it will not auto login. It wants to use the local admin account which is not what is set in my auto logon settings.
Everything else seems to work fine.
I dont think Im the only one having this problem as I have seen some other discussions on the web but I cant find a solution.
Has any one else tried this and are having or had the same problem? how did you get around it?
Cheers
Greg Turnbull
Someone help me out here, because I just cannot figure what the problem is.
We have a machine that is extremely slow when PXE'ing to our MDT server. It's the only machine that does this, so I created a Litetouch USB drive. This worked wonderfully, and I was able to boot to the MDT server to select the correct task sequence, etc.
However, I stupidly removed the USB drive too early during the whole build, and so I faced an error.
I started the process again, ensuring I ran the 'clean' command within DISKPART before beginning another build. The OS is applied fine, but when the task reaches the 'applying unattend.xml with DISM.EXE', it stays so for about 10 minutes, before presenting the dreaded 'dirty environment' window. Thinking that the DISKPART command may not have worked (it's worked fine for me in the past), I decided to boot to a Windows 7 disc, and flatten the hard disk using the standard format utility from there, before then booting from the USB drive again to begin the process. Lo and behold, I had exactly the same issue. Now the system is in a 'dirty environment' loop.
I can't understand how? - The disk has been formatted clean, and I can't understand how the machine could possibly reference a previous build from the USB drive - surely the only files present are the folders/files I created during the creation of the USB drive? Or, is the machine referencing our MDT server, and can reference a previous build that way?
Really stumped. Any help would be great. Many thanks.
Is CustomSettings.ini within Windows settingspackage the only CustomSettings.ini used when deploying workstations using MDT Task Sequence through SCCM. I mean does CustomSettings.ini in DeploymentShare\Control be ever used in this situation.
Also can i use same settings in SCCM integrated CustomSettings.ini than in plain MDT driven CustomSettings.ini?
Thought I would just post this here in case anyone was trying to do something similar. I wanted to get a notification when a build was complete so it wasn't sitting around waiting while we were busy.
I used to do this with a vbs script but with the inclusion of powershell now, it is done quite simply.
function sendMail{
$smtpServer = "mailserver.com.au"
$msg = new-object Net.Mail.MailMessage
$smtp = new-object Net.Mail.SmtpClient($smtpServer)
$msg.IsBodyHTML = $true
$msg.From = "MDT.Deployment@mailserver.com.au"
$msg.To.Add("recipient@mailserver.com.au")
$msg.subject = "Build complete : " + $env:computername
$msg.body = "$body"
$smtp.Send($msg)
}
$bios = get-wmiobject -class "Win32_BIOS" -namespace "root\CIMV2"
$computer = get-wmiobject win32_computersystem -namespace "root\CIMV2"
$scriptpath = split-path ($MyInvocation.MyCommand.Path)
$Header = [IO.File]::ReadAllText($scriptpath + "\Notification\Header.html")
$Footer = [IO.File]::ReadAllText($scriptpath + "\Notification\Footer.html")
$body = $Header
$body = $body + '<div style="line-height: 150%;">'
$Body = $body + '<br>' + "Computer Name : " + $tsenv:OSDComputername
$Body = $body + '<br>' + "Username : " + $tsenv:Administrators003
$Body = $body + '<br>' + "Model : " + $computer.model
$Body = $body + '<br>' + "Manufacturer : " + $computer.manufacturer
$Body = $body + '<br>' + "BIOS Serial : " + $bios.SerialNumber
$body = $body + '</div>'
$body = $body + $footer
sendmailSave the above as Notify.ps1 in the Scripts folder of your deployment share, then add a TS step to run a powershell script and addNotify.ps1 as the command.
Might give you enough of an idea to implement yourself.
As a note, I have two files Header.html and Footer.htmlin a sub-folder of %scriptroot%\Notification which contains a nice header and styling, and then our corporate footer - to match our helpdesk notification style. You can remove this if needed and just pass a simple html email through the PS script.
We use Administrator003 to add the user to local admins (dont ask) so that equals the user the build is for.
Obviously adjust the server name and email addresses to match your corporation, enjoy!
I had success deployment window image.
But 2 Error was found as below:
ZTI ERROR - Non-zero return code from loadstate, RC = 71
ZTI ERROR - Non-zero return code from ZTIUserState, RC = 71
Please help....