I've posted over to the Office 365 forum but didn't get much luck so I thought I would come over here.

I'm really struggling to deploy the Office 365 installation.  In fact, I'm having a hard time getting it installed full stop.

So the process I have followed is:

1. Download the Office Deployment Tool
2. Run the deployment too (which extracts setup.exe and a template for the XML file)
3. Modify the XML file to:

<Configuration><Add SourcePath="" OfficeClientEdition="32" ><Product ID="O365ProPlusRetail"><Language ID="en-us" /></Product></Add>  <Display Level="None" AcceptEULA="TRUE" />  <Logging Name="OfficeSetup.txt" Path="%temp%" /> </Configuration>

4. I've then run the setup.exe /download configuration.xml - this seems to download some files (about 1GB worth)

5. I then copy this entire folder to the C:\ of a fresh build and run 'setup.exe /configure configuration.xml'

This fails with an error in the log of:

C2R Client returned failing error code 17002

I've tried to deploy over the network form a share with 'Everyone' access and the same result.

At this point I have no idea whats going on,  does anyone have this working?

I am getting the following error, when the pc reboots, during any of the following: applying pre-application updates, installing applications, applying post-application updates on our Lenovo M73 Windows 7 desktop computers.  It doesn't happen on the Dell OptiPlex desktops or Lenovo/Dell Laptops.

The error is "A connection to the deployment share (\\server.xxx.local\DeploymentShare$) could not be made.  DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection.

If I click on retry the task sequence carries on as normal but the error can happen again when the pc reboots next.  I have tried changing the server name for the IP address and also just used the server name.  The pc is on the network correctly as I can get the IP address via IPConfig and it shows that it has a current lease as well.  If I look in device manager the network card is installed correctly and there are no devices not found.

Here is the end of the BDD log:

<![LOG[Property InstalledUpdates167 is now = 9655393d-1b46-46a2-ac21-c4d1b5e960d1]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Property InstalledUpdates168 is now = 884c7884-5970-4fd5-8afb-f52a0bd8204f]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[More to install, Please reboot and run again!]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Property SMSTSRetryRequested is now = true]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Property SMSTSRebootRequested is now = true]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[ZTIWindowsUpdate processing completed successfully.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Command completed, return code = -2147021886]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LTIDirty is now = FALSE]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property OSDTargetDriveCache is now = DIRTY]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\LiteTouch.lnk" already exists.]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property BootPE is now = ]LOG]!><time="16:49:46.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : <time="16:50:06.000+000">\\pcnumber\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\pcnumber\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"   <time="16:50:06.000+000">\\pcnumber\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : <time="16:50:06.000+000">\\pcnumber\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="16:50:06.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives =   C:]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found existing task sequence state information in C:\_SMSTaskSequence, will continue]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Not running within WinPE.]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\server.xxx.local\DeploymentShare$.
DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection.]LOG]!><time="16:50:07.000+000" date="02-28-2014" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">

Any advice would be appreciated as we are going to have a large quantity of these to roll out.

Many Thanks

James

Hi

In my customsettings.ini i have set some Applications as in Applications001= etc.

These do get ticked in the application pane wizard, but if I decide on a particular occasion I don't want to install one of the apps and I untick it, the application still gets installed.

Is this by design?  It shouldn't be obviously.

After sysprep and a reboot, I am receiving the message Specify which deployment share to usewhen capturing a Win7 x86 wim from a vm and it shows the deployment share path aX:\Deploy.  Previously I captured a Win7 x64 wim but that no longer works as well.  I've used the same deployment share to capture a Win8.1 wim.  I also used a older deployment share with the same result.  I had WAIK installed when I used MDT 2102 but removed it after this problem started.  Below are the customsettings.ini and bootstrap.ini for the deployment share.

Customsettings.ini:

[Settings]
Priority=Default
Properties=Custom

[4291-A37]
BitsPerPel=32
VRefresh=60
XResolution=1280
YResolution=768

[Default]
OSInstall=Y
DeploymentType=NEWCOMPUTER

OSInstall=YES
SkipComputerName=YES
OSDComputerName=%SerialNumber%

SkipAdminPassword=YES
AdminPassword=*********

SkipProductKey=YES

SkipTimeZone=YES
TimeZone=035

DeployRoot=\\PCS_JR6ZGQ1.us.ricoh.ds\DEPLOYMENTSHARE$
;SLShare=\\PCS_JR6ZGQ1\PCBCKUPS$
UserDomain=PCS_JR6ZGQ1
UserID=administrator
UserPassword=*********

SkipDomainMembership=YES
SkipApplications=YES
SkipWizard=NO
SkipCapture=NO
SkipFinalSummary=NO
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipUserData=YES

ScanStateArgs=/v:5 /o /c
LoadStateArgs=/v:5 /c /lac

KeyboardLocale=en-US
Userlocale=en-US
UILanguage=en-US

DoNotCreateExtraPartition=YES
DestinationDisk=0
DestinationPartition=1

UserDataLocation=NONE

Bootstrap.ini:

[Settings]
Priority=Default

[Default]

I am using the following software versions to deploy a Windows 7 SP1 x64 Lite-Touch Installation to a test machine that I am running:

Windows Server Version:  Windows Server 2012 Enterprise 64-bit

Microsoft Deployment Toolkit Version:  2013

Windows ADK Version:  8.1

I ran a default Task Sequence deployment and had no issues with the process and everything deployed fine. 

However, I now wish to customize this installation and include the Windows updates that were released after SP1.  From my understanding I can accomplish this task three ways.  The first is to let the system go out and get the updates but I tried this process and the deployment time is around 2 hours.  The second way to is to add the packages into the task sequence and the the third is to inject them into the wim.

I have imported a small group of updates into the packages folder.  Next I verified that the apply patch option in the preinstall phase was enabled and the selection was set to all packages.  The problem I run into is that none of the updates seemed to apply.  I then attempted it again by disabling the apply patch option and placing the task for install updates offline in the post-install phase and when that didn’t work I also created a custom task in the state restore phase.  No updates applied in any of these attempts.

From what I can tell (but am uncertain) the updates were not being applied since the unattended.xml did not have the packages listed there.  I tried adding the packages to the unattended file and on my next attempt using each of the phases I receive a dism.exe error.

My question is as follows:

If I wish to add updates directly to the wim file or if I want to add them into the task sequence for deployment (I would like to complete things both ways for comparison) how should I go about accomplishing this task?

Did anyone use MDT wizard studio http://mdtwizardstudio.codeplex.com/ with MDT2013?

Just wanted to check for any compatibility issues before I give a try.

Thank you!

D_Sam

Hello,

Can some sone help me with PS script to change user account pictures of all user account in windows 7 and windows 8 ?

I will deploy this through MDT TS as Custom TS after OSD.

Shailendra

Shailendra Dev

I need to delete all of our Drivers we have in MDT because we have a lot of duplicate drivers which is really slowing down our imaging process.  With our current setup it would take at least 36 hours or more to completely regenerate the deployment share.  And I found out that on some drivers we had about 60 or 90 duplicates.  So I have new set of drivers without the duplicates I need to import. 

So I went into our MDT workbench and I highlighted all the out of box drivers right clicked that window and then went to delete and told the system to completely delete all drivers even if they are in existing folders.   That was about 5 hours ago and the system has not progressed any further.  Task Manager says the system is still running (its not giving me a not responding message) but there is no activity in Task Manager the CPU usage is at 0% and the memory usage of the MMC snap in is at 16,856K with very little to no change (activity)

So that would point to me the system has frozen even thou task manager says it is still running.  So my question is this, can I just delete all the contents of the out of box drivers in the deployment folder then update the share and then import the new drivers?  By me doing a manual delete would this have other effects elsewhere?

I am starting to think having 60 or 90 duplicate drivers for each product category would cause the system to take 1 hour or 2 to deploy a system or 36 hours to update the deployment share, what do you think?  One change I did was adjust the scratch space from 32MB to 128MB.  But this problem has been happing long before I changed the scratch space.

System is a Quad Core i5 2.53, 4GB of RAM, 39 GB of Free on HDD.  Windows Server 2008 R1, MDT 2012  Otherwise the preformace of the system is normal and I don't see any hard drive problems in event viewer. 

Hi ,

Am getting Error code 1603 (fatal error during installation) while deploying the SEP through MDT task sequence . am not getting such issue regularly but some time am getting and need to be fixed.

Shailendra

Shailendra Dev

Hi sir

when i turn on only speed led is on and led's auto andstamina are off

also when i touch assist key and vaio key nothing happend

also function keys not work (for mute key f2 and....)

pls help me to solve these problems 

(windows xp is run on my loptop ) (model vaio vpcz116gx/s)

Hi,

I try to capture a custom image but at the end of the process, I get the following error (see attached image):

ZTI ERROR - Unhandled error returned by ZTIWindowsUpdate: ActiveX component can't create object (429)

Could someone help me to solve this please?

I have been editing the CustomSettings.ini so that different task sequences install different pieces of software. See the below for an example (there is more but I have removed some);

[Settings]
Priority=TaskSequenceID,Default
Properties=MyCustomProperty

'Default Settings
[Default]
_SMSTSOrgName=Super Amazing Place                        deploy01
OSInstall=Y
SkipPackageDisplay=TRUE
InputLocale=en-GB
SystemLocale=en-GB
UserLocale=en-GB
KeyboardLocale=en-GB
EventService=http://DEPLOY01:9800

'Adobe Reader
Applications001={43558e95-034e-4a98-acae-75ab0fbdaa9f}

'Quicktime
Applications005={778f6ba9-e9a8-454d-b708-18516a9aefa3}

'Build2 Settings
[0015]

'AppV 4.6
MandatoryApplications001={f2f2222c-c8e5-47f0-bed9-6ec7837bc088}

All seems to work however I have found an issue. If I choose the task sequence Build2 [0015] in the Wizard but then decide to go back and choose the normal build (Build1 [0010]) it will still apply the Build2 [0015] settings and have the box for AppV 4.6 [MandatoryApplications001] ticked. It also happens the other way around so if I choose Build1 [0010] and then find I need to go back to Build2 [0015] it will not have any of the Mandatory Applications ticked.

This could be a major problem as we have several complicated builds and it is quite possible someone might choose the wrong build/task sequence at the first step and then click back to change it. If the person building the machine has not checked the applications (and why would they the build is meant to determine software) it could mean software being installed on the wrong machines which may have licencing implications.

I know that you can complete the software install in the task sequence itself but I want it to be a shown option (even if it is Mandatory) during the Wizard.

All help apppreciated.

I want to confirm if Redirected Folders (Documents, Music, etc) will be backed up via USMT and restored on the users computer. The whole idea is to ensure that the remote sites with poor connectivity do not have to pull all documents from the WAN that are already stored in cache on their computer. When the user logs into their Win7 machine that is refreshed, I expect that the Redirection/Offline files GPO will reconcile and make sure all the contents on the server are up to date with what's stored on the refreshed computer.

For this to work do I need to add the registry key that is referenced in this KB?

http://support.microsoft.com/kb/942960/en-us

Thanks.

I've been using MDT for a few years now and seem to got Windows 7 deployments down. I created my first 8.1 Sysprep and Capture TS and am running into an issue. It seems to be failing at the Win PE step before sysprep. I have made sure my DS is updated, CS.ini is correct as far as I know, MDT 2013 with 8.1 ADK... I sysprepped and captured my Win 7 images fine. This is my first Win 8.1 GM image. Is there something obvious I am missing?

Windows 8.1 Ent. MDT 2013

In my TS, i am running Copy scripts (cscript.exe "%SCRIPTROOT%\LTICopyScripts.wsf") under Postinstall. I have added MoveOU.vbs file in Scripts folder. Edit LTICopyScipts.wsf file and Include this file.

 ScriptsToCopy = Array("LiteTouch.wsf", "ZTIUtility.vbs", "ZTIGather.wsf", "ZTIGather.xml", _
   "Wizard.hta", "Credentials_ENU.xml", "Credentials_scripts.vbs", "WizUtility.vbs", "Wizard.css", _
   "Wizard.ico", "BackButton.jpg", "plusicon.gif", "minusico.gif", "DeployWiz_Definition_ENU.xml", _
   "DeployWiz_Initialization.vbs", "DeployWiz_Validation.vbs", "MoveOU.vbs", "Summary_Definition_ENU.xml", _
   "Summary_scripts.vbs", "LTICleanup.wsf", "LTIGetFolder.wsf", "ZTINICConfig.wsf", _
   "ZTINICUtility.vbs","ZTIBCDUTILITY.VBS", "ZTIDataAccess.vbs", "LTISuspend.wsf", _
   "ZTIDiskUtility.vbs", "ZTIRunCommandHidden.wsf", "header-image.png", "NavBar.png", "Computer.png")

But Tasksequence fails when it runs Move OU. I did f8 but didn't find MoveOU.vbs file. So it is failing to copy this file. Does anyone run into this issue or any suggestion???

orion

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?

Hi All, Pls help me with prerequisites list to install MDT

I need the prerequisites fo all versions of MDT (2010, 2012, 2013)

Thanks, Prabha G

Hello!

I have a problem with an application install on Windows 8.1. I'm trying to install two applications and have activated "Reboot the computer after installting this application" for the first application. After rebooting the deployment window does not show up agagin. BDD.log shows, that the deployment starts after the reboot but seems to hang, before the UI shows.

I tried to install this two applications under Windows 7, which works without any problems.

Here is the BDD.log for the failed deployment: http://pastebin.com/PbUH1LUq

Can anyone confirm this problem with MDT 2013 and Windows 8.1? Any ideas how to fix this?

I have a task sequence in MDT to deploy Win7. It all works perfectly (including joining to the domain when finished) but the computer name entered in the Windows deployment wizard:

is ignored later on and must be reinputted on the 'Set up windows' wizard. 

My Rules on the deployment share are:

Any help would be greatly appreciated - I'm new to this :)

Alex