Hi,
Guys,
How to configure Task Scheduler in mdt,
To run scripts via Task Scheduler.
Configure Task Scheduler
↧
↧
Capturing windows 8
I was toying with windows 8 deployment and was busy capturing a windows 8 image but when it was taking a while i checked with trace what was going.
when imagex scans the disk to capture it seems to do a lot of ignoring extended attributes before finally starting the capture.
never had this happen with windows 7 captures so i take it windows 8 uses a lot of extended attributes on files.
i read on the imagex page that it doesn't support these extended atributes but i'm sure it isn't the intention to increase deployment times by +/- 30 minutes just because imagex has to go through your disk saying it is ignoring certain attributes.
is there anyway to stop imagex from taking it's sweet time with windows 8 captures?
i am using a standard client task sequence.
↧
MDT 2012: When a Refresh deployment was made to a Windows 7 x64 computer to refresh it to Windows 7 x86, computer could not startup.
The client computer to be refreshed had a Windows 7 x64 installation , and had a 100MB system reserved volume.
Then I want to refresh the x64 to x86 with the Task Sequence of Windows 7 x86.
From within the client computer, I manually excuted scripts\BDD_Autorun.wsf from the deploymentshare folder on the MDT server.
In the Task Sequence of Windows 7 x86, I disabled the "format and partition disk" step. And I set the "Install Operating System" as "Next available formatted Partition".
After the deployment finished, the computer restarted automatically and stopped at a screen, which said that the Volmgr.sys has someting wrong.
Could some one tell me how to solve this problem?
Thanks a lot!
↧
Update Deployment Fails - Error: 0xc150003a An error occurred while loading DISM. The DISM tool may be corrupt.
OK, I am stumped I can't get this to work... I am running this on a Windows 7 Professional 64bit Box joined to the domain (I have domain admin rightswith Microsoft Windows AIK & Microsoft Deployment Toolkit 2012 installed.
- Add new Deployment Share - accept all defaults
- Import Operating System from Windows 7 Professional cd created from iso downloaded from Microsoft
- Create Task Sequence - accept all defaults
- Unchecked x86 checkbox on Deployment Share Properties
- Update Deployment Share
- Receive the following output:
=== Making sure the deployment share has the latest x86 tools ===
=== Making sure the deployment share has the latest x64 tools ===
=== Processing LiteTouchPE (x64) boot image ===
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x64 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files\Windows AIK\Tools\PETools\amd64\winpe.wim will be used.
WIM file mounted.
Set Windows PE system root.
Set Windows PE scratch space.
Added component winpe-hta
Added component winpe-scripting
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Error: 0xc150003a
An error occurred while loading DISM. The DISM tool may be corrupt.
Try reinstalling DISM.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = -1051721670
DISM /Add-Package failed for component C:\Program Files\Windows AIK\\Tools\PETools\amd64\WinPE_FPs\winpe-wmi.cab, rc = -1051721670.
Added component winpe-wmi
Added component winpe-securestartup
Added component winpe-fmapi
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Error: 0xc1500023
An error occurred while attempting to access the image at C:\Users\tleanna\AppData\Local\Temp\MDTUpdate.5084\Mount.
For more information, review the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = -1051721693
DISM /Add-Package failed for component C:\Program Files\Windows AIK\\Tools\PETools\amd64\WinPE_FPs\winpe-mdac.cab, rc = -1051721693.
Added component winpe-mdac
Copying files...
Copying WIM to the deployment share.
Creating an ISO.
Copying ISO to the deployment share.
=== Completed processing platform x64 ===
=== Processing complete ===
I create the boot CD and all it does is reboot the machine... What is going on?
↧
Migrate MS Communicator 2007 to 2007
Hi All,
How to migrate all settings from MS Communicator 2007 - 2007 using USMT 5.0?
Need to migrate offline address book too...
Can any one have any idea about it?
Thanks
Divakar
↧
↧
MDT 2012 : How to install Windows 7 into a hard disk already having a Windows 7 in it with a 100MB system reserved partition as the Partition 1 ?
Maybe this operation shoud be called "Refresh Operation":
A hard disk of a computer already had a Windows 7 x64 Edition installed in it with a partition of 100MB as the system reserved partition and a partition named "OSDisk" of 50GB which had the Windows 7 system in it.
System reserved partition was the partition 1 of disk 0.
"OSDisk" partition was the partition 2 of disk 0.
Then, I wanted to install a x86 Windows 7 on it to repalce the x64 Windows 7 in the "OSDisk" partition.
And all the data in the other partitions could not be deleted.
Then , in the MDT task sequence of a Windows 7 x86 Edition, I disabed the "Format and Partition Disk" step, and I set the "Install Operating System" step to "Logical drive letter stored in a varible" and "OSDisk", like below:
Then I booted the client computer from Lite Touch PE x86 , after the OS deployment process finished, an error screen was displayed like below. It said the Volmgr.sys was missing or damaged.
How can I do?
By the way, can some one tell me how to do in the task sequence to meet the need of these 2 situation below:
Situation 1: OS had been installed in the partition 1 of disk 0, no any other system reserved partitions.
Situation 2: A system reserved partition of a certain capacity (for example 100MB) already existed which was the partition 1 of disk 0 , and the OS partition was the partition 2 of disk 0. It is just like many normal Windows 7 installation with DVD.
Thank you !
↧
LiteTouch WIM being created without sysprep.exe
I tried to do a capture, but it kept failing. Checked the logs and its failing when it can't find the sysprep.exe file. Open command prompt and sure enough there is no sysprep in the X:\ path where it is looking. Go back to the MDT server and extract the .wim then drill down to the sysprep folder and it has nothing in it either.
I've made sure I have the latest version of MDT 2012 and WAIK, but it just seems to refuse to include the sysprep.exe.
Hopefully someone has a fix for this.
↧
Computer Description
Im using MDT 2012. I'm trying to set the computer description so that I can automate my deployment more. How can I achieve this?
Another thing that I'm looking to do is trying to set my company specific user icon so that every computer I deploy Win7 to it has this set as its icon.
Any kind of thoughts or help would be awesome!
Thanks!
↧
MDT 2012 cannot create multicast namespace in WDS
I've researched this quite a bit and I'm unable to figure it out. Any help is appreciated.
I'm using a 2008 R2 server with MDT 2012 and WDS. It's a VM and configured with two hard drives. The deployment share is e$\DS and it's share permissions are Everyone:Read, System:Full, and my user name:Full. I can add a boot image to WDS and we configured IP Helper for PXE boot and it's working. When I try to configure MDT for multicast it fails. I do not have an existing Multicast Transmission in WDS. The RemoteInstall folder also exists on the e$ and is written to properly when a Boot Image is added. I've read various articles and most focus on multicast failing or performance issues with it, not the failure to actually create the transmission entry.
The error I'm getting in MDT when I update is:
Error Code: 0xC110010A
Error Description: The specified namespace name is invalid. The name must be 1 to 255 characters long
(Japanese text)
Unable to create multicast namespace "e$\DS", rc = -1055915766.
If there is any other information I can provide please let me know. Thanks!
↧
↧
Always confusing me! Automatically selecting the partition or the volume where the cunrrent OS installation exists ?
This problem has been always confusing me for a long long time. By many many tests, reading many many threads, I just can not solve this yet!
There are many PCs.
Some have Volume 1 as the OS partition that is active. While some have Volume 1 as the Syetem Reserved Partition (100MB as the Windows 7's boot partition,active), and volume 2 as the OS partition.
Any partition behavior is prohibited.
How can MDT 2012 automatically selecting the partition or the volume where the current OS installation exists . Only format this partition or volume and apply new OS image to the partition. I think MDT obviously has some way of detecting whether a partition is the current OS partition.
Regardless of the current operating system:
- When Windows XP image applied to PC with Volume 1 as the current OS partition , format the partiton and keep the OS partition active.
- When Windows XP image applied to PC with Volume 1 as the Syetem Reserved Partition (100MB as the Windows 7's boot partition) and volume 2 as the current OS partition， format the volume 2 and make the OS partition active, and make the 100MB partition unactive.
- When Windows 7 image (x86 or x64) applied to PC with Volume 1 as the OS partition , format the partiton and keep the OS partition active. Automatically generate the BDE files in the same partition.
- When Windows 7 image (x86 or x64) applied to PC with Volume 1 as the Syetem Reserved Partition (100MB as the Windows 7's boot partition, active) and volume 2 as the current OS partition，format the volume 2, apply image to this parition, keep the Volume 1 active, and refresh the 100MB BEDdrive correctly.
↧
Capture-image hangs on "create wim"
Hello,
i am capturing a new Windows 8-image.
I have created a seperate task-sequence for Windows 8-capture with the DVD of windows 8 as setup-files.
After rebooting to Winpe my deployment this is hanging op "create wim"
What to do?
↧
What happens during "Expanding Windows Files" phase of installation?
I've got my WDS/MDT deployment of Win7 Prof working a treat so I've been doing some performance testing.
When I'm on the office LAN, the "expanding Windows file" stage of deployment takes around 15 mins.
If I take the server to a remote office with a 2MB link back to the domain controllers etc the same phase is around 45 mins.
Could someone tell me what is happening during this phase that could be introducing this sort of delay? Is there anything I could do to speed it up (short of putting a domain controller in a remote office).
Thanks.
↧
Is there a script to make MDT 2012 to automatically determine which volume to install OS to, according to the volume size?
Is there a script to make MDT to automatically determine which volume to apply OS image to, just selecting between Disk 0 Volume 1 or Disk 0 Volume 2 ?
For the Task Sequence to deploy Windows 7 :
1) If volume 1 < 500MB and > 99MB, then install the OS to volume 2 and make the volume 1 to be primary, active and BDEDrive with no driver letter.
2) If volume 1 > 500MB, then install the OS to volume 1 , and make the volume 1 to be primary, active, and BDEDrive.
=================================================================================
For the Task Sequence to deploy Windows XP :
1) If volume 1 < 500MB and > 99MB, then install the OS to volume 2 and make volume 2 to be primary and active.
2) If volume 1 > 500MB, then apply the OS image to volume 1 and make the volume 1 to be primary and active.
↧
↧
What script/function adds local administrators for lite touch
Hi
I'm trying to find what function does reads the property Administrators(*) and add this to local administrators group. I've found the file OSDLocalAdmins.vbs but cannot figure out when/if this is executed for the TS. Another file that looks promising is ZTIGroups.wsf but I cannot figure out where it adds local admins from Administrators001 ... 00x.
↧
WDS - Installation finished but i get some error massage - the netzwork password is not correct
Hi,
But the strange thing is that the error appiers sometimes.
The installation seems to be okay, all applications are installed...
Get someone the same error or have a solution?
Regars
Strizi!
↧
Restoring the Quick Launch tool bar with USMT 4
I have a client that prefers to restore end users' Quick Launch tool bat when migrating from XP to Win 7. They are using MDT 2010 U1 and USMT 4. Scanstate calling MigApp.ml and MigUser.xml does capture the folder /file structure of each user ( %APP_DATA%\microsoft\Internet Explorer\Quick Launch...) but does not restore it to the expected location. any ideas?
Thanks!
Dale
↧
MDT 2012: Force MININT and _SMSTaskSequence on C Drive
Hi,
I'm deploying Windows 7 X64 using MDT 2012, I format 3 partitions at the beginning of the task sequence and I assign them specific drive letters during the state restore phase.
I had no problem with MDT 2010 but since I'm using MDT 2012 MININT and _SMSTaskSequence folders are created on partition 2 so when I assign my drive letters deployment fails.
I tried to force SMSTSLocalDataDrive in cs.ini but it seems that MDT doesn't care, I can see in the variables.dat that the C drive is selected but folders are still in my second partition.
Any help?
I'm deploying Windows 7 X64 using MDT 2012, I format 3 partitions at the beginning of the task sequence and I assign them specific drive letters during the state restore phase.
I had no problem with MDT 2010 but since I'm using MDT 2012 MININT and _SMSTaskSequence folders are created on partition 2 so when I assign my drive letters deployment fails.
I tried to force SMSTSLocalDataDrive in cs.ini but it seems that MDT doesn't care, I can see in the variables.dat that the C drive is selected but folders are still in my second partition.
Any help?
My Blog: DeployXP [Under Construction]| Viadeo: Mathieu Ait Azzouzene | Linkedin: Mathieu Ait Azzouzene
↧
↧
Custom Setup Window Possible in WinPE/MDT?
Is it possible to display to the user the custom windows setup window that allows users to format/partition any installed hard drive in the WinPE environment? Currently I have three task sequences. The first one is a standard wipe & load. The second one creates a C: and a D: partition and installs the OS on C:. The third option does a wipe & load on C: and leaves D: intact.
I am wondering if it is possible to give the user the option to format a second partition before proceeding with one of the three above task sequences. When I go to manually install Windows, it allows me to hit the "Custom Install" button and brings up a window where I can delete, create, and format partitions. This window is what I am looking for in WinPE.
Can I set this up through MDT?
↧
Force windows to boot Sysprep on first boot
Hi there, I am trying to force windows 7 & 8 too boot into sysprep on first boot after being deployed and before putting in Keys or anything. Is this even possible?
I am not using a capture image as our systems are too different from each other. I have tried using MDT and adding the tasks in the unattend.xml with audit and OOBE but neither seems to work. I know I can press ctrl shift F3 when it reaches the point when it asks me for a key but I want to automate that (kinda) and also wonder if i can still run automated installs of programs after it?
↧
Zero touch USMT error
Hi,
I am doing zero touch installation and below is my cs.ini settings.
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipUserData=YES
SkipDeploymentType=Yes
DeploymentType=REFRESH
SkipDomainMembership=Yes
SkipTaskSequence=Yes
TaskSequenceID=001
SkipComputerName=Yes
SkipComputerBackup=YES
ComputerBackupLocation=NONE
ComputerName=asd
SkipLocaleSelection=Yes
UILanguage=en-US
UserLocale=en-US
KeyboardLocale=0409:00000409
SkipTimeZone=Yes
TimeZoneName=India Standard Time
SkipBitLocker=Yes
SkipSummary=Yes
Bu tit throws error when it runs for usmt task.Please let me know what is missing from my side.
Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"
↧
More Pages to Explore .....
