MDT2010 - Unable to mount the WIM, so the update process cannot continue

May 5, 2010, 9:50 am

≪ Previous: Hyper-V: A onnection to the deployment share could not be made (invalid credentials

My system: HP 6910p laptop running Windows 7 Enterprise x64.

Trying to use 2010 to develop a x64 Windows 7 Enterprise image. I get the following error when I attempt to update the deployment share:

=== 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:\DeploymentShare\Operating Systems\Windows 7 x64\Sources\boot.wim will be used.

Unable to mount the WIM, so the update process cannot continue.

=== Completed processing platform x64 ===

　=== Processing complete ===

(Does the same for the x86 portion)

I've seen the posts about not finding the correct WIMGAPI.DLL and have made sure they are the correct version in the c:\windows\system32 and C:\Program Files\Windows Imaging. I even put C:\Program Files\Windows Imaging as the first dir in my path followed by c:\windows\system32. I have full control of the share and ntfs permissions on the server. I created a new deployment share on my C: drive to eliminate the server but it does the same thing. I turned off my AV, got the same error.

Ran Sysinternals Process Monitor while I updated the deployment share and it had several entries for the wimgapi.dll. The Process Monitor operation descriptions were QueryNetworkOpenInformationFile and CloseFile for \\<Server>\deployment$\Tools\x86\wimgapi.dll This was on the server. The other operation descriptions were QueryOpen, CreateFile, QueryNetworkOpenInformationFile and CloseFile for C:\Program Files\Windows AIK\Tools\x86\wimgapi.dll. When you look at the Process Monitor properties of both of these wimgapi.dll's the process tab shows c:\windows\system32\wimgapi.dll as the dll in memory which is the correct version. In fact, all the locations described have the correct version. I'm stumped. Anyone know how I can get this to update the deployment share?

Thanks

Unable to mount the WIM, so the update process cannot continue

↧

HP Switch

March 22, 2013, 1:32 am

≫ Next: MDT 2012 - Unable to capture image

≪ Previous: MDT2010 - Unable to mount the WIM, so the update process cannot continue

Hi,

I know this forum is not for Switches but can someone direct me where I can post my question? I have HP E5412zl switch. Some couple of weeks ago I saw the POE status light flashing so I restarted the Switch. The flashing seemed to have gone away after the restart but to my supprise, it came back again. Is there any probem with the POE or.. I don't know.

Someone should kindly help me.

sameyaw

↧

MDT 2012 - Unable to capture image

May 1, 2012, 12:32 pm

≫ Next: MDT 2010u1. English KeyboardLocale with Russian UserLocale.

≪ Previous: HP Switch

Hello everyone,

I ran the LiteTouch.vbs from the reference computer and start the 'sysprep and capture' task. When I click Next to begin, the next window is at 'Ready to begin' and all I can do is to click Begin. After that, I get to the Success window with the message"Operating system deployment completed successfully." and nothing got captured at all.

I wasn't able to get the screen for capturing location at all. Do anyone knows what is going on? There is no logs for me to look at.

↧

MDT 2010u1. English KeyboardLocale with Russian UserLocale.

March 22, 2013, 5:25 am

≫ Next: MDT 2010 - Post deployment can't continue for some reason

≪ Previous: MDT 2012 - Unable to capture image

I'm using MDT 2010 Update 1 for deploying Windows XP and Windows 7. LiteTouch without SCCM. Windows has Russian localization. But keyboard locales must be English (en-us) as main and first locale, and Russian (ru-ru) as second locale.

But before a start of deploying process Ready-wizard shows KeyboardLocale=ru-ru;0419:00000409. This abnormal setting applies to a deployment of Windows 7. This is not what I want.

Bootstrap.ini:

[Settings]
Priority=Default

[Default]
DeployRoot=\\WDS\DeploymentShare$

KeyboardLocalePE=0409:00000409;0419:00000419
KeyboardLocale=0409:00000409;0419:00000419

SkipBDDWelcome=YES

CustomSettings.ini:

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=NO
SkipBitlocker=YES

TimeZone=145
TimeZoneName=Russian Standard Time
BackupDrive=ALL

UILanguage=ru-ru
UserLocale=ru-ru
KeyboardLocale=0409:00000409;0419:00000419
KeyboardLocalePE=0409:00000409;0419:00000419

SkipLocaleSelection=YES

I didn't find any solution of this problem. Debug of DeployWiz_languageUI.vbs (script in MDT) shows me that the modification of KeyboardLocale variable is inLocale_Validation function in this script.

There is not any sence of a such sort of validation.

Is there any workarounds to this problem which don't involve script modification?

↧

MDT 2010 - Post deployment can't continue for some reason

March 21, 2013, 3:48 am

≫ Next: MDT 2012 - unable to join domain

≪ Previous: MDT 2010u1. English KeyboardLocale with Russian UserLocale.

Environnement: Windows Server 2008 R2 + MDT 2010 + Win7x64 Pro

Dear guys,

I hope you'll be able to help me.

Through a Task Sequence, I installed the Windows Enterprise and some software then I captured to a new xxxx.wim.

I imported the new WIM and created a new Task Sequence to deploy this new WIM.

When I deploy the new WIM, in the first Windows Boot, it should enter the machine into the domain, finalize the MDT deployment task sequence etc... instead of that, for some reason it can't log on automatically with the Built-in Administrator account. I have no idea why.

If I check Unattend.xml file, under point 7 oobeSystem, amd64_Microsoft-Windows-Shell-Setup_neutral, I have the good informations by default.

Do you know why it can't get into Windows automatically in order to finalize the process please ?

↧

MDT 2012 - unable to join domain

March 22, 2013, 5:46 am

≫ Next: MDT 2012 keeps rebooting to USB and trys to do a new deployment

≪ Previous: MDT 2010 - Post deployment can't continue for some reason

My customsettings.ini is working in all senses so i figured i would add computers to the AD and OU based on Type, i e Desktop models should be added to the OU=PC, DC=name, DC=local

so here is the layout of my additions:

[Settings]
Priority=ByType,ByVMType,Default
Properties=MyCustomProperty

[Default]
SkipBDDWelcome=YES
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipTaskSequense=NO
SkipAdminPassword=YES
AdminPassword=P@ssw0rd
SkipComputerName=NO
ComputerName=Datornamn_here
SkipDomainMembership=YES 
JoinDomain=name.local
DomainAdmin=joindomain
DomainAdminDomain=name.local
DomainAdminPassword=JoinDomain
MachineObjectOU=OU=Computers,DC=NAME,DC=local

[ByType]
SubSection=Laptop-%IsLaptop%
SubSection=Desktop-%IsDesktop%

[Laptop-True]
MachineObjectOU=OU=Laptop,DC=NAME,DC=local

[Desktop-True]
MachineObjectOU=OU=PC,DC=NAME,DC=local

Now i don't get any of my computers added to the AD and the ZTIDomainJoin.log tell me only this:

JoinDomain_error_log

Even in NetSetup.log i can find the corresponding error:

NetSetup_error_log

What is it i am not seeing here? Where is the error i need to correct?

As soon as the TS is done i get the error from the computer saying it has tried to may times to join the domain, but i can at this point manually add the computer to the domain with no issues (other than that it ends up in the COMPUTER-OU)...

I have found similar posts here but no definitive answer to the question. I can and will provide more information about this if needed.

Anyone?

↧

MDT 2012 keeps rebooting to USB and trys to do a new deployment

March 21, 2013, 5:35 am

≫ Next: Task Sequence Doesn't Start After OS Install

≪ Previous: MDT 2012 - unable to join domain

Our company is moving to MDT to deploy images. I had our image on a thumb drive to load. it works perfectly. I recently added one more set of drivers to inject for a specific desktop. Now the only changes I made to the entire task sequence was add the drivers and the if statement to it would inject them. After the OS is installed, it reboots but boots back to the thumb drive (it did not do this before) oddly the BIOS is configured to boot HD first. I have to close out and pull the thumb drive and put it back in so it can then install the apps. Any ideas on where to check to see what may be the issue? Thanks.

↧

Task Sequence Doesn't Start After OS Install

March 20, 2013, 1:35 pm

≫ Next: Administrator autologon fails in some cases Win 7 MDT 2012

≪ Previous: MDT 2012 keeps rebooting to USB and trys to do a new deployment

To best explain here are the steps I've taken to create my custom WIM file.

1. Using VMWare workstation I installed Win 7 x64, ran updates, and installed the base programs for my image.

2. Ran Sysprep and Captured an image of this machine. (This is run by LiteTouch.vbs as a task sequence I created in Deployment Workbench.)

3. On a test computer I PXE booted and selected my image from the Task Sequence Wizard. Another part of my wizard has choices for which programs you would like to install once the OS is completed. (Office 2013, Google Chrome, etc.)

4. Windows 7 installs and I am taken to the login screen - - I log in with Administrator account.

5. At this point the Task Sequence should continue on with the Installation of Applications but this never happens.

From here I browsed to my deployment share and to the Scripts folder and double click the LiteTouch.vbs to try and continue the task sequence. I receive an error that a Dirty Environment was found. I have tried to figure out why my task sequence isn't completing when I first log into Windows. Has anyone else experienced this issue?

↧

Administrator autologon fails in some cases Win 7 MDT 2012

March 22, 2013, 2:09 pm

≫ Next: [SOLVED] MDT2012 Computer Name not set via OSDComputerName in CS.INI

≪ Previous: Task Sequence Doesn't Start After OS Install

Ok, so now I have tried "everything". My Windows 7 deployment process is almost perfect, but I still have one small obstacle to overcome before I'm content.

The problem is this:

When I deploy Windows 7 through MDT/WDS to a new "unknown" PC; one thatnever has been joined to the domain, the first admin loginalways fails. However, when I redeploy a machine that has been joined to the domain before, the login works. I should add that this is true even though I delete the computer account from AD and (of course) repartition and format the disks. If I, on the other hand, prestage the computer account in AD the login still fails when it's a brand new PC.

In our domain we have a GPO that changes the name of the local admin account, and my first thoughts were that this policy isn't always applied in time for the first login occurance. This seems to be true when it comes to new PCs; the admin account is sometimes still called "Administrator". But it is not true when it comes to a computer that has been part of the domain before, again EVEN THOUGH I delete the account from Active Directory. In my unattend.xml file I tell the deployment process to use the new administrator name and the correct password as set by the GPO. Is there anyway I can force this account name and password to be set earlier in the process to ensure that the login is successful? I tried theApplyGPOPack string in customsettings.ini, but that GPO is applied too late (after login) to be useful. Can I apply the GPOs earlier? What am I missing here?

Cheers for your help!

/JSWB

↧

[SOLVED] MDT2012 Computer Name not set via OSDComputerName in CS.INI

June 12, 2012, 8:38 am

≫ Next: DaRT Tools with Windows Recovery in x64 - not available ?

≪ Previous: Administrator autologon fails in some cases Win 7 MDT 2012

I'm using 2 user exit scripts as well as another custom property to set computername. In the end it looks like this

OSDComputerName=%Site%-%SysModel%-%SysSerial%

After much testing (via cscript //nologo \\server\deploymentshare$\scripts\ztigather.wsf /debug:true /inifile:\\server\deploymentshare$\control\customsettings.ini) , I can confirm the OSDComputerName variable I'm setting in my CustomSettings.ini (CS.ini hereinafter) is getting set properly.

I successfully deployed a test image to sample machine & I found myself looking at the Computer Name setup screen that was pre-filled with just 'PC'. I clicked next & let the rest of the task sequences complete. At the end I looked at the BDD.LOG in C:\Windows\Temp\DeploymentLogs where I could see the variable was set, but not used.

Property OSDCOMPUTERNAME is now = WA-X20-1234567
Using from [DEFAULT]:" OSDCOMPUTERNAME = WA-X20-1234567
...further down...
No value found for ComputerName
...further down...
//settings[@pass="specialize"]/component[@name="Microsoft-Windows-Shell-Setup"]/ComputerName not found in C:\MININT\Unattend.xml, unable to update.
...further down...
No value found for ComputerName
...further down...
//settings[@pass="specialize"]/component[@name="Microsoft-Windows-Shell-Setup"]/ComputerName not found in C:\MININT\Unattend.xml, unable to update.

I checked the Unattend.xml for the Task Sequence in question and the ComputerName property (Under 4 specialize -> x86_Microsoft-Windows-Shell-Setup_neutral) is blank, and the 'Write Empty String' isnot checked.

What have I done wrong?
Should the 'Write Empty String' be checked?
Is it expecting '%ComputerName%' or '%OSDComputerName%' in the 'ComputerName' property of the Unattend.xml?
Do I have to create a new VBScript to set the environment variable? (essentially negating what I've already done in the CS.ini)

Many thanks!

↧

DaRT Tools with Windows Recovery in x64 - not available ?

March 23, 2013, 11:35 pm

≫ Next: Automatic domain joining Task Seequence rules for xp-Win7 migration when DHCP not available

≪ Previous: [SOLVED] MDT2012 Computer Name not set via OSDComputerName in CS.INI

Hi,

I am testing Windows Recovery and DaRT tools (with WinRe) on x86 and x64 machines.

I have followed http://social.technet.microsoft.com/Forums/en-US/mdt/thread/192a81d5-0ff4-48d7-93ff-12f0c5a9f439/) to have DaRT integrated into Windows recovery. I am not able to see DaRT Tools if I boot x64 machine in Windows Recovery mode (REagentC.exe /boottore) but if a reboot any x86 machine I am able to see DaRT tools in Windows Recovery. I am not sure where I have missed something. The only difference I have for x64 is that its a VM and x86 is a physical machine...does it make any difference to DaRT availability (I assume I should not). Is it something a knows issue\bug ?.....Any pointers pls.

Regards,

↧

Automatic domain joining Task Seequence rules for xp-Win7 migration when DHCP not available

March 24, 2013, 6:01 am

≫ Next: Getting "Windows could not parse or process the unattend answer file for pass [specialize]" with IE10 integration? Read this...

≪ Previous: DaRT Tools with Windows Recovery in x64 - not available ?

Hi Every One,

Greetings for the Day.

I recently promoted to MDT team in my Org.I have been assigned for a migration project (XP to Win7Prof).The TCP/IP properties configuration is done statically in the entire organisation(SCCM not Avail)Facig problem with "Domain Joining"I am able to capture all the TCP/IP properties automatically,and getting ping reply from Primary Dns and NSLookup happening when I try with the IP address of PC .But domain joining failure Error occureing at the Final Summary.

Please help me to resolve this issue.

Thanks

N.V.Srinivas,

vedadri_nvs@hotmail.com.

↧

Getting "Windows could not parse or process the unattend answer file for pass [specialize]" with IE10 integration? Read this...

March 15, 2013, 6:22 pm

≫ Next: Dual boot LTI Media with Windows server 2003 SBS for an emergency partition restore

≪ Previous: Automatic domain joining Task Seequence rules for xp-Win7 migration when DHCP not available

Hey guys,

I just discovered an issue with using MDT to integrate Internet Explorer 10 into Windows 7 & 2008 R2 image files. Building the images was no problem at all, but when I tried to deploy them it would bomb with this error every time:

"Windows could not parse or process the unattend answer file for pass [specialize]."

So a very annoying and cryptic error to say the least. Obviously the issue was with the unattend.xml file that gets auto-generated by MDT, but all the items under "specialize" had worked just fine when I built the image and the IE version was the only item that had changed. After comparing the Windows 7 & Server 2008 R2 unattend.xml files to my Windows 8 & Server 2012 unattend.xml files (because they have IE 10 native) I discovered that the following flag was missing from the Windows 8 & Server 2012 unattend.xml files:

<IEWelcomeMsg>false</IEWelcomeMsg>

So I simply commented it out like so:

Re-ran my test deployment and viola, 100% successful with zero errors. I was a little embarrassed/annoyed that this took me so long to track down, then I realized others might be struggling with this too so thought I'd share.

Hope my time spent saves someone else some grief!

↧

Dual boot LTI Media with Windows server 2003 SBS for an emergency partition restore

March 25, 2013, 2:00 am

≫ Next: Capturing windows 8

≪ Previous: Getting "Windows could not parse or process the unattend answer file for pass [specialize]" with IE10 integration? Read this...

Scenario

A ready system with C: OS 100GB, D: Data rest of the HDD space.
OS is Windows Server 2003 SBS promoted to domain with lot of applications installed
Couldn’t do sysprep as OS was promoted to domain, hence relied on imagex.
Took two separate images of C: and D:
Created a custom task sequence to restore both the images after partitioning harddrive
Working as desired, without any issue

New Expectation

To add an addition partition of size 5GB and dump LTI media contents
Use this as an alternative to LTI media to reimage C: & D: incase of OS corruption, virus etc

Success till now

Able to create additional partition R:
Able to copy all media contents to R:
Not able to setup dual boot between OS and R: using bcdedit to manage boot configurations

Steps taken

As per my search I need to modify Win2K3 bootloader to Vista Boot loader by using below command

Command

bootsect.exe -NT60 c: /force

Output

Target volumes will be updated with BOOTMGR compatible boot code.

c: (\\?\Volume{b927...e6963})

Updated NTFS filesystem bootcode. The update may be unreliable since the volume could not be dismounted during the update:

Access is denied

Bootcode was successfully updated on all targeted volumes

As the above command returned a “Access is denied” error. I connected my HDD with LTI media contents and re-executed this command. This time is completed without any error and I boot to OS.

Now I needed to add legacy entry in BCD, So I ran BCDEdit to list all entries

Command

Bcdedit /enum all

Output

The boot configuration data store could not be opened.

The system cannot find the file specified.

I have tried many ways after this like below with no good outup

Imported bcd from LTI media and added legacy entries
Created new store, added legacy entries and LTI entries(not sure as it should be RAM disk)

Help me achieve a dual boot LTI environment with Windows server 2003 SBS. Thanks in advance.

↧

Capturing windows 8

August 22, 2012, 7:58 am

≫ Next: Applying Updates Fails

≪ Previous: Dual boot LTI Media with Windows server 2003 SBS for an emergency partition restore

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.

↧

Applying Updates Fails

March 25, 2013, 2:32 am

≫ Next: Task sequences containing "Install roles and features" and "PowerShell scripts" are failing when a PowerShell execution policy is set by a GPO

≪ Previous: Capturing windows 8

Hi guys,

Having problems deploying Windows 7 with MDT. Installing without any updates works fine and everything installs successfully.

When installing updates via the patches process the install fails giving an error of failed to apply unattend settings, but there is nothing recorded in the setupact or setuperr logs.

If I do install windows updates offline nothing happens. I've tried using the 3rd party WSUS Offline updates download tool as well but this doesn't work either.

Any help much appreciated as always,

JT.

Joel Thornton Windows 7 Ultimate x64, Windows 7 Ultimate x32, Windows XP x32

↧

Task sequences containing "Install roles and features" and "PowerShell scripts" are failing when a PowerShell execution policy is set by a GPO

March 25, 2013, 1:20 am

≫ Next: Windows 8 activation through MDT

≪ Previous: Applying Updates Fails

Hi all

We are currently facing some troubles with the new PowerShell feature in MDT 2012 Update 1. Let me shortly describe our environment. We use MDT 2012 Update 1 version 6.1.2373.0 and WADK to deploy Windows Server 2008 R2 images. At the moment PowerShell 2.0 is installed on deployed servers. All servers are joined to an AD and placed into a dedicated OU. There are several GPOs linked to that OU. One specific GPO sets the PowerShell execution policy to remote signed.

At the moment all task sequences running PowerShell scripts (ZTIPowershell.wsf) are going to fail during the deployment process of a server. Even worse no roles and features are going to be installed as for Windows Server 2008 R2 with PowerShell 2.0 the internal MDT PowerShell host Microsoft.BDD.TaskSequencePSHost35.exe is used as well. In the log file ZTIOSRole.log an error is reported for each role or feature (see log file further down). But if the GPO containing the execution policy setting is disabled all roles and features are going to be installed smoothly. Moreover the task sequences running the PowerShell scripts are processed without an error as well. Are there any known problems using the MDT PowerShell host in conjunction with execution policies set by GPOs?

Your help is very much appreciated. Many thanks!

Stephan Kuhnen

ZTIOSRole.log:

<![LOG[Property Parameters is now = -FeatureName Desktop-Experience]LOG]!><time="09:01:27.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[PowerShell version detected: 2.0]LOG]!><time="09:01:27.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[About to run: "C:\MININT\Modules\Microsoft.BDD.TaskSequenceModule\Microsoft.BDD.TaskSequencePSHost35.exe" "<SERVERNAME>\DeploymentProd$\Scripts\ZTIOSRolePS.ps1" "C:\MININT\SMSOSD\OSDLOGS" -FeatureName Desktop-Experience]LOG]!><time="09:01:27.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property Parameters is now = ]LOG]!><time="09:01:27.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ERROR - Desktop-Experience role processing via PowerShell failed, rc = 10904]LOG]!><time="09:01:27.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="3" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles001 is now = APPLICATION-SERVER]LOG]!><time="09:01:27.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles002 is now = RDS-RD-SERVER]LOG]!><time="09:01:27.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles003 is now = NET-FRAMEWORK-CORE]LOG]!><time="09:01:27.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles004 is now = DESKTOP-EXPERIENCE]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property Parameters is now = -FeatureName GPMC]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[PowerShell version detected: 2.0]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[About to run: "C:\MININT\Modules\Microsoft.BDD.TaskSequenceModule\Microsoft.BDD.TaskSequencePSHost35.exe" "<SERVERNAME>\DeploymentProd$\Scripts\ZTIOSRolePS.ps1" "C:\MININT\SMSOSD\OSDLOGS" -FeatureName GPMC]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property Parameters is now = ]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ERROR - GPMC role processing via PowerShell failed, rc = 10904]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="3" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles001 is now = APPLICATION-SERVER]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles002 is now = RDS-RD-SERVER]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles003 is now = NET-FRAMEWORK-CORE]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles004 is now = DESKTOP-EXPERIENCE]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles005 is now = GPMC]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property Parameters is now = -FeatureName RSAT-Print-Services]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[PowerShell version detected: 2.0]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[About to run: "C:\MININT\Modules\Microsoft.BDD.TaskSequenceModule\Microsoft.BDD.TaskSequencePSHost35.exe" "<SERVERNAME>\DeploymentProd$\Scripts\ZTIOSRolePS.ps1" "C:\MININT\SMSOSD\OSDLOGS" -FeatureName RSAT-Print-Services]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property Parameters is now = ]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ERROR - RSAT-Print-Services role processing via PowerShell failed, rc = 10904]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="3" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles001 is now = APPLICATION-SERVER]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles002 is now = RDS-RD-SERVER]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles003 is now = NET-FRAMEWORK-CORE]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles004 is now = DESKTOP-EXPERIENCE]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles005 is now = GPMC]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles006 is now = RSAT-PRINT-SERVICES]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property Parameters is now = -FeatureName Telnet-Client]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[PowerShell version detected: 2.0]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[About to run: "C:\MININT\Modules\Microsoft.BDD.TaskSequenceModule\Microsoft.BDD.TaskSequencePSHost35.exe" "<SERVERNAME>\DeploymentProd$\Scripts\ZTIOSRolePS.ps1" "C:\MININT\SMSOSD\OSDLOGS" -FeatureName Telnet-Client]LOG]!><time="09:01:28.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property Parameters is now = ]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ERROR - Telnet-Client role processing via PowerShell failed, rc = 10904]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="3" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles001 is now = APPLICATION-SERVER]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles002 is now = RDS-RD-SERVER]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles003 is now = NET-FRAMEWORK-CORE]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles004 is now = DESKTOP-EXPERIENCE]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles005 is now = GPMC]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles006 is now = RSAT-PRINT-SERVICES]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles007 is now = TELNET-CLIENT]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property Parameters is now = -FeatureName XPS-Viewer]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[PowerShell version detected: 2.0]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[About to run: "C:\MININT\Modules\Microsoft.BDD.TaskSequenceModule\Microsoft.BDD.TaskSequencePSHost35.exe" "<SERVERNAME>\DeploymentProd$\Scripts\ZTIOSRolePS.ps1" "C:\MININT\SMSOSD\OSDLOGS" -FeatureName XPS-Viewer]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property Parameters is now = ]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ERROR - XPS-Viewer role processing via PowerShell failed, rc = 10904]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="3" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles001 is now = APPLICATION-SERVER]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles002 is now = RDS-RD-SERVER]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles003 is now = NET-FRAMEWORK-CORE]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles004 is now = DESKTOP-EXPERIENCE]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles005 is now = GPMC]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles006 is now = RSAT-PRINT-SERVICES]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles007 is now = TELNET-CLIENT]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles008 is now = XPS-VIEWER]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[One or more roles were not processed successfully]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[FAILURE: 1: Server 2008 R2 Role Processing]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="2" thread="" file="ZTIOSRole">
<![LOG[ZTIOSRole processing completed successfully.]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Validating connection to <SERVERNAME>\Events]LOG]!><time="09:01:29.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Already connected to server G0AARE-INST0001]LOG]!><time="09:01:30.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41001 sent: ZTIOSRole processing completed successfully.]LOG]!><time="09:01:30.000+000" date="03-14-2013" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">

↧

Windows 8 activation through MDT

December 3, 2012, 3:00 pm

≫ Next: Installing Windows 7 with MDT 2010 on VHD drive D:\

≪ Previous: Task sequences containing "Install roles and features" and "PowerShell scripts" are failing when a PowerShell execution policy is set by a GPO

I haven't had a chance to test very much but from what I have read, you should be able to install a retail copy of Win 8 on an OEM machine and it will pick up the key stored in the BIOS automatically. I'm trying to deploy Windows 8 to an OEM PC and it is not picking up any product key at all.

Am I reading this wrong?

For a comparison, we used to deploy a thick image to our Lenovo laptops and use the COA key (post install) to activate Windows. Obviously this is not possible with Windows 8 as the COA sticker is not provided.

EDIT:: Installing with the DVD works and seems to pick up the OEM product key, but deploying the same DVD with MDT 2012 U1 doesn't. Anyone have any advice on this please?

↧

Installing Windows 7 with MDT 2010 on VHD drive D:\

March 25, 2013, 6:18 am

≫ Next: Problems with VMWare installation after ADK and MDT2012

≪ Previous: Windows 8 activation through MDT

I want to deploy windows 7 on vhd on drive d: with MDT 2010. I managed to do everything (normal install) except repartition inside vhd (creating two partitions -- c:\ drive and d:\ drive and installing OS to drive D:). Can anyone suggest anything or point me into right direction?

What i have to do is: on drive c:\ i ahve to have vhd file and then boot vhd file so that OS is installed on d:\ - i drop all changes every reboot and data mut be on c:\ drive - application limitation

Lenart

↧

Problems with VMWare installation after ADK and MDT2012

March 25, 2013, 6:25 am

≫ Next: Sysprep fails with CloneTag

≪ Previous: Installing Windows 7 with MDT 2010 on VHD drive D:\

I've been having a problem since moving to Windows ADK and MDT 2012 for Windows Deployment and trying to install to a virtual machine. I used to be able to do this with no issue with WAIK. I've found a few posts here and there saying to import the driver from the VMWare tools folder, however, that doesn't seem to really help. I am able to boot into MDT and select the installation, however, once the installation kicks off it comes up with an error saying that it's unable to find disk 0 and that it could be a storage drive issue. I'm not entirely sure how to resolve this issue, but would really appreciate some insight if anyone has found a solution for this one. I appreciate the help! Thank you!

↧

Latest Images