Admaine

Hi All, I'm hoping someone can help with this issue, I will provide a little background before introducing the problem to try and make my situation as clear as possible. Background - I have recently upgraded MDT from 2010 to 2013 and integrated Windows Assessment and Deployment Kit for Windows 8.1 - My task sequences are split into two folders (x86 and x64), both of these folders contain a deployment image for our commonly purchased PCs. They have been created using a sysprep and capture which was working swimmingly. - The first time I imaged two new 64x PCs since the upgrade, MDT went through the installation OK (it took all day which is unusual but it did complete), the speed of installation was going to be my next issue however I was faced with a bigger one. Problem We have received two new 64x PCs which I am trying to image, however the deployment wizard errors and cancels at the stage of 'Installing Operating System', with the following error: Litetouch deployment failed, Return Code = -2147467259 0x80004005 Failed to run the action: Install Operating System. Incorrect function. (Error: 00000001; Source Windows) The execution of the group (Install) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source Windows) Failed to run the last action: Install Operating System. Execution of task sequence failed. Incorrect function. (Error: 00000001: 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 This seemed strange as I haven't touched anything since the last successful image. I've been researching the following error and the first thing that I initially tried was to Completely Regenerate the Boot Images when updating the deployment share. Since then I can no longer PXE boot to the 64x WDS, instead it eventually brings up command prompt with X:\windows\system32 that sits on top of the Microsoft Solution Accelorator background, nothing else happens at this point. If I boot to the 32x WDS if does load the deployment wizard where I can actually see the 64 bit task sequence, if however I try to run this I'm prompted with that exact same error above. The second thing I tried was disabling 'Injecting the drivers' as I thought that the network driver may have been causing a problem and disconnecting me from the deployment share, this however didn't work either. I'm totally baffled now to be honest and would appreciate anyone helping me out? Many thanks in advance, Ad

Thanks a lot guys, I will look at making the switch to GPP

OK I've just figured this out although I still don't fully understand it. At the time I was logged on as my personal account which I'd manually given Admin access to due to not wanting to enter my local admin UAC credentials for every install (you know how frustrating it is). Having just logged in as one of the standard AD users it automatically mapped them, at which point I removed my admin access and logged back in which then mapped them as it should. Unsure as to why the admin access matter though?

Yes I can map them manually no problem. If I locate the logon script (on the Win 10 PC) via \\domain_name\SYSVOL\domain_name\Policies\{Policy ID}\USER\Scripts\Logon and run this batch file the drives map fine, it just doesn't do when a user logs on. Any other ideas at all? Thanks

Hi, Thank you for your reply. To expand a little on our setup which will hopefully help our situation, we use Win 7 Enterprise throughout the business, all PC's\Laptops run a logon script which firstly maps 3 network drives using the standard command below: net use P: \\Server\Share /persistent:yes net use R: \\Server\Share /persistent:yes net use H: \\Server\Share\%username% /persistent:yes net config server /autodisconnect:-1 All these work as they should, however this same command is not running for the Windows 10 Enterprise PC that I'm testing. This script is located in USER CONFIGURATION\WINDOWS SETTINGS\SCRIPTS (LOGON\LOGOFF)\LOGON This same script also includes 4 lines which copies company PDF's (from a network location) to users desktops, this part of the script is working on the Windows 10 PC, it's just not mapping the drives. Does this basic script still require me to copy the ADMX and ADML files into the location you posted? Hope this adds to a further explanation of my problem. All help is much appreciated. Ad

OK, I have managed to get the documents to appear on the desktop at Logon which is one of my two goals achieved however there is still no mapped drives. Can anyone possibly shed some light on this? Do the drive mappings deploy differently to Win 10 PCs? Thanks again, Ad

OK, I have managed to get the documents to appear on the desktop at Logon which is one of my two goals achieved however there is still no mapped drives. Can anyone possibly shed some light on this? Do the drive mappings deploy differently to Win 10 PCs? Thanks again, Ad

Hi All, I am currently testing a Windows 10 Enterprise PC to see how it performs with our companies internal applications as we are looking to upgrade to the new operating system in the future. One snag I have come across is Group Policy, we don't utilise this probably as much as we should, however we do use it to deploy logon scripts which quite simply map 3 network drives which everyone in the business has access to and additionally copies Company Handbooks, Health & Safety manual etc to users desktops. These same two tasks aren't running on the Windows 10 PC, therefore when I login there are no mapped drives and no documents on the desktop. I am no expert on GPO so really could do with some help, if I run the scripts manually (by navigating to \\domain_name\SYSVOL\domain_name\Policies\{Policy ID}\USER\Scripts\Logon) the network drives map, the documents that should copy to the desktop don't. I have been reading up as much as possible with regards to the administration templates, however I'm not entirely sure we use them (as when I browse to \\domain_name\SYSVOL\domain_name\Policies\{Policy ID}) there is only the following folders visible: - Group Policy - Machine - User - GPT (configuration settings) I'm after any real guidance that could help get this (hopefully simple task) up and running for the Windows 10 PC. All our other PC's\Laptop run Windows 7 and the scripts work as they should. Many thanks in advance , Ad

Hi All, I am currently testing a Windows 10 Enterprise PC to see how it performs with our companies internal applications as we are looking to upgrade to the new operating system in the future. One snag I have come across is Group Policy, we don't utilise this probably as much as we should, however we do use it to deploy logon scripts which quite simply map 3 network drives which everyone in the business has access to and additionally copies Company Handbooks, Health & Safety manual etc to users desktops. These same two tasks aren't running on the Windows 10 PC, therefore when I login there are no mapped drives and no documents on the desktop. I am no expert on GPO so really could do with some help, if I run the scripts manually (by navigating to \\domain_name\SYSVOL\domain_name\Policies\{Policy ID}\USER\Scripts\Logon) the network drives map, the documents that should copy to the desktop don't. I have been reading up as much as possible with regards to the administration templates, however I'm not entirely sure we use them (as when I browse to \\domain_name\SYSVOL\domain_name\Policies\{Policy ID}) there is only the following folders visible: - Group Policy - Machine - User - GPT (configuration settings) I'm after any real guidance that could help get this (hopefully simple task) up and running for the Windows 10 PC. All our other PC's\Laptop run Windows 7 and the scripts work as they should. Many thanks in advance , Ad