Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all 11297 articles
Browse latest View live

ZTIWindowsUpdate takes for ages to start after adding the KB3125574 rollup.

0
0

Hi all, I Made a working Build and Capture TS. Used the default Windows 7 install.wim everything works fine. The Pre-App Windows Updates search and install starts after 3 times within 5min.
(using the latest WUA Version: 7.6.7601.19161). First 150 updates then anonther 90 updates. Capture is fine and after xx hours i have a complete Win7 capture.

Now the problem:

To save time I offline updated the original install.wim with the required prereq (KB3020369) and added the KB3125574 (Win7 SP1 convenience rollup) to the MDT packages. when I use this offline updated install.wim it takes hours to start the The Pre-App Windows Updates search and begining the install of the rest of the updates.

So with original install.wim starting to update image within 3 tries and 5min.

With updated install.wim starting to update image withing 3 tries and many hours and still 123 updates to go. (including .net)

WUA = Latest version

Does anyone have an idea what causes this problem?

------------

Logging from working and original install.wim:


Property SMSTSRetryRequested is now =  ZTIWindowsUpdate 13-5-2016 10:25:29 0 (0x0000)
Configuring client to use WSUS server http://XXXX0004.dev.XXX.nl:8530 ZTIWindowsUpdate 13-5-2016 10:25:29 0 (0x0000)
Configuring Windows Update settings (manual update, use server) ZTIWindowsUpdate 13-5-2016 10:25:29 0 (0x0000)
Windows Update Agent verion 6 found, OK to continue ZTIWindowsUpdate 13-5-2016 10:25:31 0 (0x0000)
Ready to Opt-In to Microsoft Update: WUA Version: 7.6.7601.19161 ZTIWindowsUpdate 13-5-2016 10:25:31 0 (0x0000)
Microsoft Update Service:  Enabled = False ZTIWindowsUpdate 13-5-2016 10:25:31 0 (0x0000)
Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0 and Type = 'Software'] ZTIWindowsUpdate 13-5-2016 10:25:31 0 (0x0000)
Start Search... ZTIWindowsUpdate 13-5-2016 10:25:31 0 (0x0000)
INSTALL - 57260dfe-227c-45e3-9ffc-2fc77a67f95a - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2656356) - 4 MB ZTIWindowsUpdate 13-5-2016 10:30:33 0 (0x0000)

------------

Logging from updated install.wim:

Begin Windows Update. Reboot=[false]  Retry=[true]  Count = 2 ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Property MSIT_WU_Count is now = 3 ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Property SMSTSRebootRequested is now =  ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Property SMSTSRetryRequested is now =  ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Configuring client to use WSUS server http://XXXX0004.dev.XXX.nl:8530 ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Configuring Windows Update settings (manual update, use server) ZTIWindowsUpdate 18-5-2016 08:44:09 0 (0x0000)
Windows Update Agent verion 6 found, OK to continue ZTIWindowsUpdate 18-5-2016 08:44:12 0 (0x0000)
Ready to Opt-In to Microsoft Update: WUA Version: 7.6.7601.23435 ZTIWindowsUpdate 18-5-2016 08:44:12 0 (0x0000)
Microsoft Update Service:  Enabled = False ZTIWindowsUpdate 18-5-2016 08:44:12 0 (0x0000)
Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0 and Type = 'Software'] ZTIWindowsUpdate 18-5-2016 08:44:12 0 (0x0000)
Start Search... ZTIWindowsUpdate 18-5-2016 08:44:12 0 (0x0000)
INSTALL - 57260dfe-227c-45e3-9ffc-2fc77a67f95a - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2656356) - 4 MB ZTIWindowsUpdate 18-5-2016 13:52:57 0 (0x0000)
INSTALL - 6502a461-7262-48fc-b567-f8d3c2f82ae6 - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2604115) - 23 MB ZTIWindowsUpdate 18-5-2016 13:52:57 0 (0x0000)
INSTALL - 78f92451-801a-40f5-9582-cb8d1ca993be - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2729452) - 13 MB ZTIWindowsUpdate 18-5-2016 13:52:57 0 (0x0000)

---------------------------------------------

This is what I did to update the install.wim offline:

Used the original install.wim from the Win7 SP1 sources

(expand not required but I did)
Downloaded the KB3020369 (req) and the rollup KB3125574.

expand -F:* F:\Update\AMD64-all-windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu F:\Update

expand -F:* “F:\Update\Windows6.1-KB3020369-x64.msu” F:\Update

dism /mount-wim /wimfile:C:\install.wim /mountdir:C:\Mount /index:1

dism /image:C:\mount /Add-Package /PackagePath:C:\Update\Windows6.1-KB3020369-x64.cab

dism /image:C:\mount /Add-Package /PackagePath:C:\Update\Windows6.1-KB3125574-v4-x64.cab

dism /unmount-wim /mountdir:C:\mount /commit

After that copied the install.wim back to the OS deployment shares directory I used.

Started the Build Ref Win7 Tasksequence on a VM (2cores 10GBmem)

WUA Version: 7.6.7601.23435 (latest)

MDT 2013 Update 2 - Windows 2012 R2 Server

ZTIWindowsUpdate.log - The Good file : https://onedrive.live.com/redir?resid=749BF03D0E7EF0BB%211611

ZTIWindowsUpdate.log - The wrong file: https://onedrive.live.com/redir?resid=749BF03D0E7EF0BB%211612




Building a Win10 reference image - 7 questions about MDT

0
0
I am working on an a (semi-)automated Litetouch reference image of Windows 10 x64 Ent. with most applications installed. I have run into several issues along the way. I hope someone will spare the time to enlighten me on some of them :)

1. Can a Task Sequence become corrupt?
I have seen solutions on Technet sometimes suggesting to recreate a Task Sequence in different scenarios. I have right now a problem with at TS not starting sysprep in my reference image, but seem to skip it, and instead reboot Windows 10 back to the desktop in an inconsistent state (share mounted but disconnected, no admin right but still logged in as Administrator etc.). When I made a new TS and began building it, it worked again - so far.

2. WDS or not? 
Would I benefit using WDS to deploy images, if I cannot benefit from PXE boot? I would have to use a Discovery image (on a USB stick preferably).

3. Windows Update steps and installing applications
What is best practice when using both Windows update steps (using WSUS) and also install applications in a reference image.

The default TS setup is pretty simple:

- Windows Update pre
- Install applications
- Windows Update post
- (Custom Tasks)

A guide on Technet suggest this:

- (Custom Tasks - pre Windows update)
- Install basic stuff (.NET, VCRedist etc.)
- Restart
- Windows Update pre
- Install application
- Windows Update post
- (Custom Tasks - post Windows update)

The latter seem more safe, but perhaps it introduce more complexity than necessary?

5. Do I need to re-import Applications, when I update either source files or install-script?

6. Hanging deployments
Sometimes my deployments or captures are hanging, just because there are too many connections to my MDT server. Cleaning up dead connections often resumes whatever MDT is doing. Is this normal? I would assume some automatic cleanup process would happen whenever a TS completed?

7. Purple restart screen on first reboot after deployment
This is maybe a bit bizarre question, but I have had some issues with my reference image, where the restart screen, after the initial deployment to a PC, would become purple when it restarted for the first time. Booting back to the desktop, it briefly appears again, but from here on it is only blue as expected on every reboot/startup. No relevant entries in Event logs, Setuperr.log or Setupact.log. No system file errors either. Would you start deploying an image, if you knew this happened? I have a bad feeling about it.




.net 4 Microsoft is amazing

0
0

Another day another ridiculously pathetic and annoying problem, is it ie11? is it java? no it is .net 4.

Because the ie11 installer is basically broken, i thought let me slipstream the new (in)convenience update and ie11 in to a wim to update our image in mdt.

Problem is after booting up in to my new image to install applications .net 4 is not installed, why that was not included in the (in)convenience update or ie11, I will never know.

But sure i accept that MS couldn't run a bath, so let me try slipstream 4.6.1 in to the wim as well. Nope there is no msu for .net only a rubbish web installer and offline installer. no msi either. Wonderful job.

Ok let me create an application for .net in the task sequence. Should work right because that is straight forward?

WRONG! won't install just hangs, i tried 3 different .net 4 installers and none of them work.

Great job guys

Unattend.xml file not always being applied

0
0

Hi all,

Been having an issue since updating to MDT 2013 Update 2, whereas a task sequence's Unattend.xml file will not always apply.

I have a Windows 10 Pro x64 task sequence, with an Unattend.xml file configured with some information (Copy Profile (which includes desktop background), skip all the OOBE screens, create a "local admin" user, etc.). 

If I deploy this to a VM, all works fine. If I deploy this to a Surface Pro 3, it's not being applied (the desktop background isn'T being applied, the local admin user isn't being created, etc.). 

At first I thought it was a problem with the Unattend.xml, so I recreated it from scratch (I usually use an XML template file), and it still didn't work. 

Here is a ZIP file with both, a working and non-working BDD.LOG files: https://www.dropbox.com/s/fv2mljhszlld6d6/Working_Deployment_VM.zip?dl=0

Is there something I'm doing wrong ? I used to do this exact same thing before updating to MDT 2013 Update 2 and it was working fine. 

Thanks in advance! :)

EDIT: Got some extra info that might help.

I looked deeper into the logs, and found that for my Surface Pro 3 deployment, MDT tries to merge server Unattend with the local one, while the VM test doesn't.

Here are the lines from the SP3 log: 

Loaded C:\MININT\unattend.xml	ZTIConfigure	5/24/2016 11:30:31 AM	0 (0x0000)
Merging \\SLMTL-WDS01\DeploymentShare$\Control\WIN10-007\Unattend.xml into C:\MININT\unattend.xml	ZTIConfigure	5/24/2016 11:30:31 AM	0 (0x0000)
Loaded \\SLMTL-WDS01\DeploymentShare$\Control\WIN10-007\Unattend.xml for merging	ZTIConfigure	5/24/2016 11:30:31 AM	0 (0x0000)
Searching for unattend[@xmlns='urn:schemas-microsoft-com:unattend']	ZTIConfigure	5/24/2016 11:30:31 AM	0 (0x0000)
Adding new child unattend[@xmlns='urn:schemas-microsoft-com:unattend']	ZTIConfigure	5/24/2016 11:30:31 AM	0 (0x0000)
Merge complete.	ZTIConfigure	5/24/2016 11:30:31 AM	0 (0x0000)

Whereas the log from the VM only shows the very first line.

I looked at older pre-MDT 2013 Update 2, for SP3 deployments, and only the first line showed up.

How could I go about preventing this "merging" from happening, since it's clearly not working properly ?

Sysprep error when building a Windows 10 Reference image (UPDATED)

0
0

(I have updated the question below)

Hi,

I receive this error when the build process initiates sysprep. I uninstall some apps offline during Post-Install, but the error always points to one of the apps, I want to keep in the image. Perhaps it is not related, even though Microsoft suggests this is the cause:

Sysprep fails after you remove or update Windows Store apps that include built-in Windows images

I have found two suggested solutions (Sysprep broken in Windows 10 Build 9926)

1. Make sure the virtual machine you are using for reference images never connects to Internet.

2. Prior to run sysprep, have the task sequence delete all updated packages using PowerShell.

First option is not possible for me – I need the reference image to be online.

The second option is the same as Microsoft suggests. But how can I use a Task Sequence to delete only updated packages automatically before sysprep kicks in?

Adding the setuperr.log:

2016-05-24 20:40:15, Error                 SYSPRP Package Microsoft.WindowsAlarms_10.1510.12020.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

2016-05-24 20:40:15, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

2016-05-24 20:40:15, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

2016-05-24 20:40:15, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2016-05-24 20:40:15, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2016-05-24 20:40:15, Error                 SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x3cf2
2016-05-24 20:40:15, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2016-05-24 20:40:15, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2


I did not remove theMicrosoft.WindowsAlarms App.

Also adding some logs (I am a little desperate to get some help on this issue):

smsts.log

BDD.log

UPDATE:

I believe I know the cause of this issue now. My build process takes more than an hour, because we have some rather large applications to install. If Windows 10 is online for more than 1 hour, it starts staging appx packages. It is these packages that sysprep does not like. So it has nothing to do with the already uninstalled apps.

If I run this after sysprep has failed:

Get-AppxPackage –Allusers | Select PackageUserInformation, Name

I get this list:

Sysprep fails at the first staged package - the WindowsAlarms.

So perhaps my question should be:

- How can I remove these staged packages?
- If I uninstall theses staged packages, will it have an impact on new users for whom I want these apps to work?








MDT 2013 Update 2 BitLocker Failure OSSKU not defined

0
0

At the end of my deployment I am getting

FAILURE: False: Verify %OSSKU% is defined.

I am deploying Windows 10 Enterprise LTSB. 

What am I doing wrong here?

Litetouch.lnk not starting on laptops after first boot

0
0
I have a strange problem that only applies to laptops when they have it has been installed more than one time.
BDD.log shows
<![LOG[Found existing task sequence state information in C:\_SMSTaskSequence, will continue]LOG]!><time="12:53:46.000+000" date="05-24-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LTIDirtyOS is now = FALSE]LOG]!><time="12:53:46.000+000" date="05-24-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Creating startup folder item to run LiteTouch.wsf once the shell is loaded.]LOG]!><time="12:53:46.000+000" date="05-24-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\LiteTouch.lnk" created.]LOG]!><time="12:53:46.000+000" date="05-24-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
the Litetouch.lnk does not start the litetouch.wsf on the first boot of laptop computers. If I manually start litetouch.wsf script the deployment continues and all other tasks continue automatically after every boot. Any suggestions?

MDT 2013: "No operating system found" after Windows 7 USB deployment. Requiring USB drive to boot local OS.

0
0

Hey there,

Could use a little help in figuring out why, and how to remedy an issue I am having.

So I am using the latest MDT 2013. I have been doing network based deployments with no issue, and now I need to have a USB deployment due to some environments having a lack of infrastructure.  I created a stand alone USB media deployment. I am using a standard task sequence with a pre-configured WIM of W7. After creating the media, and copying it to my USB drive, I commence to loading it on one of the laptops I have. The initial load goes fine and the computer restarts for the first time to get ready to load into my freshly installed Windows. Here is where things get hairy...

The computer tells me "No operating system found..." blah blah blah. After some tinkering I figure out a little more info. For the loaded OS to continue, I had to tell the laptop to boot from my USB drive, not the OS hard drive. So to get the computer to boot at all, I have to select to boot from USB.

So here is what I have concluded thus far: The deployment somehow altered the boot settings of my deployment drive. It no longer boots into an MDT/PE environment, but now is required to boot from to load the local OS.

Obviously the deployment somehow altered my USB drive as some type of local OS boot partition. What is causing this to happen and how should I remedy this?


Cannot remove prompt for credential request to connect to shares...

0
0

HI folks.  I'm trying to skip the Credentials request screen during MDT startup before it asks for the image to push.  I've included the following in both Customsettings.ini and bootstrap.ini:

UserID=administrator
UserDomain=DOMAIN NAME HERE
UserPassword=PASSWORDHERE

I've updated the share fo course but it still prompts every time.  What do I have to do to get rid of this prompting?  Thanks.

ifM63x64.sys 0xC0000098 error on deployment after WinPE has installed the OS and rebooted

0
0

First, YES I have searched through this forum for an answer and still nothing has worked.

As I mentioned in the title, WinPE runs through the deployment tasks, installs the OS and reboots.  Nothing out of normal other than after installing the OS it takes an unusually long time to apply the unattend.xml

After restarted we get the error message in the title ifM63x64.sys missing or corrupt.  0xC0000098.

We are not injecting any LAN drivers into the OS, however removing the inject drivers in the task sequence all together does not correct the issue either.

LAN drivers are injected into WinPE, however none of them are iSCSI and WinPE doesn't have an issue.

I have started the reference computer, with no issue, and searched the entire registry for FCoE and come up with no entries.  The driver installed is not iSCSI but rather e1d62x64.sys.

Searching the Driver Store for ifM* returned 0 results.

Any suggestions on a next step?

How to update/maintain a deployment image - MDT 2013

0
0

Hello folks,

Using MDT 2013, I have successfully created a deployment share to build/capture a reference image - and in turn - created another deployment share to deploy that captured image to computers.  All along, I've been using various TechNet articles and other online sources to learn how to do this.  Now I want to perform maintenance on the deployment image (e.g. Microsoft updates, modifications to the default user profile etc... ), however, I  can't seem to find anything online explaining the methodology to do so.  I know I'll need to do a sysprep and capture of the reference image, but I'm confused on what would be the "Best Practices" in doing so.  Can anybody here refer me to a guide/tutorial/reference material on image maintenance in MDT?  It can be a book or an online source....

Thank you,

Adrian

Powershell script issue with MDT 2013

0
0

I have some powershell scripts in my task sequences in the MDT server. Most of them are working except one that involves calling the -filepath parameter. The filepath is point to the scripts folder of MDT to retrieve a file. However, it kept failing because the deployment could not find the path. I tried put the actual pathname as well as the variailable e.g. "%scriptroot%\filename" and they failed the same.

Any idea?

Thanks

Custom Desktop Wallpaper not being applied during deployment to Surface Pro 3

0
0

Hi all,

Been having an issue with our Surface Pro 3 and Windows 10 ever since MDT 2013 Update 2 was installed a few weeks ago (might just be a coincidence). 

No matter what I do, our custom desktop wallpaper is not being applied during the deployment. Instead, we'll be greeted with a solid black background, not even the default Hero Win10 wallpaper.

Before Windows 10, we used to have a task in our Task Sequence called "Copy OEM Folder", which would copy our custom "img0.jpg" file from our Deployment Share to the right path (%windir%\Web\Wallpaper\Windows) while the OS was still offline. This worked fine, until Windows 10, where it would just show a solid black background instead of our company wallpaper.

I tried many things back then, with no success. I ended up setting our company wallpaper as the background for the Administrator image of our custom image, which would then be copied over to every new user account on the computer through the "CopyProfile" function in the TS's Unattend.xml file. 

This worked fine, until I created a new Win10 custom image from scratch and upgraded to MDT 2013 Update 2, and am now back to square one.

Even though my captured image's Administrator account has our custom wallpaper set as background, the new profiles only have a solid black background. Note that this issue only happens with Surface Pro 3 tablets. If I take the image and deploy it to a VM or a desktop computer, it works fine.

I have tried many things: 

  1. Re-enabling the "Copy OEM Folder" task in our TS: The file gets copied and replaces the default Hero wallpaper, yet the OS does not seem to recognize it as I am greeted with a black wallpaper. If I open the personalize menu, I see my custom wallpaper as the first and default one...if I click on it, then it works, but just for the current user.
  2. I read somewhere that by default, Windows 10 searches in "%windir%\Web\4K\Wallpaper\Windows" for an image file with the appropriate resolution (img0_2160x1440.jpg). I have thus taken our custom wallpaper, resized it to 2160x1440 (the default Surface Pro 3, named it "img0_2160.1440.jpg", made sure the size was small enough (40kb), and made sure it was deployed to the right path with our "Copy OEM folder" task: Nothing, still a solid black background.
  3. Tried #2 but I used different resolutions (aka, I replaced all the current wallpapers at "%windir%\Web\4K\Wallpaper\Windows" with our custom wallpaper, resized and renamed to all the resolutions in the folder) : Did not work
  4. Read on the web some guy was simply deleting and/or renaming the "%windir%\Web\4K\Wallpaper\Windows" folder to prevent Windows from looking into it: Did not work.
  5. In the Unattend.xml answer sheet, you can set your desktop background through the "DesktopBackground" settings in "7 oobeSystem > amd64_Microsoft-Windows-Shell-Setup_neutral > Themes". I copied our desktop wallpaper, "sidlee_background_big.jpg" to "%windir%\System32" folder, and set the DesktopBackground setting to "%windir%\System32\sidlee_background_big.jpg": Did not work, still a solid black background.

Am I missing something here ? Some different access rights necessary for Windows 10 ?

We want to avoid having to go the manual way of setting the wallpaper for each user OR having to set it up using a GPO, because we want our branding there yet not prevent the user from changing it themselves.

Thanks in advance!

Where is the location of the Deployment Share stored in the .wim or .iso of the boot image?

0
0

Hello,  

I need to know where the deployment share location is stored on the litetouch_x86 or x64 boot media.  I need this information for trouble shooting an issue I am having with it pointing to the wrong deployment share, even after "Completely regenerated the Boot Images".  

Any input on the problem would be helpful, but I still would really appreciate knowing the actual location in the .wim where the it points to location of the deployment share.

Thank you.

Operating Systems giving Invalid Credentials

0
0
We have Windows MDT 2013 in our environment and while running the LiteTouch.vbs we run into a credential issue. We are able to connect to the share no problem but we only get the credential invalid error when running the LiteTouch.vbs from a Windows 8.1 Pro machine. Windows 10 and Windows 7 pro machines run the script as it is intended. Is this an issue with MDT 2013 latest update?

SCCM1511 - Setting Computer name - Task Sequence Variable "Name" - Failing

0
0

Hello,

We are building a W10 image with sccm1511 as the deployment tool and have basic success deploying basically the raw W10 ISO.  Now we are trying to build upon our success.

Why would this task sequence fail in SCCM 1511 with Windows 10?  It works in SCCM2012 with Windows 7 64bit no problem! 

In SCCM2012 we name our computers with a "Set Task Sequence Variable.

Computer Name (Laptop) - Name

OSDComputername - Is set as the Task Sequence Variable

W7L-%SERIALNUMBER% - Is set as the value.

Thank you,

Tony H.

MDT 2013 Update 2 W10 Task Sequence Stalling

0
0

So I've been trying really hard to resolve this issue I've been having and doing as much research as I can to try and get it working, but alas, it isn't working.

I have a server with MDT 2013 Update 2 that I do both Windows 7 and Windows 10 deployments on. I only do basic imaging, no USMT or anything along those lines. When I do Windows 7 installation task sequences, it works just fine. Everything goes through without a hitch. However, when I do a Windows 10 Deployment Task Sequence, everything is working just fine until after the AutoLogin goes through, and then the TS simply stops. I'll outline some things below to help see what I see:

  1. The AutoLogin to the builtin Local Admin account succeeds
  2. The deployment share drive is mapped
  3. There is no MININT folder on the root of C:\
  4. The C:\Windows\Temp folder has the deployment logs, but their update is from the capture (I have to admit I'm not extremely familiar with the log paradigm. I may need help with what I need to look for).
  5. I can make the TS proceed by doing one of two things: 
      - I can open the mapped drive and start the LiteTouch.vbs. It says it finds a dirty environment and then I tell it not to start a new one, and it ends up going through.
      - I can log out of the user and log back in, same account, and it says it finds a dirty environment and then I tell it not to start a new deployment and it also goes through.

Here's what I've tried so far:

  1. I've tried commenting out the LTICleanup line that enables UAC for the local admin
  2. I've tried recreating the task sequence and the Unattend.xml
  3. I've tried recapturing the image (Hyper-V
  4. I've tried rebuilding the PE boot image, in case there was something earlier in the process that would cause any issues.
  5. Baseball bat... 'nuff said.

I'm at a loss and I'm not sure what to look at. The nice thing is that there is a workaround to getting this for each deployment, but it's a little bit frustrating and causes an extra step of interaction in the middle of the deployment that should be unnecessary.

I may also need your help to tell me what logs you need and at what point in the process you need them from. As noted above, I'm not extremely familiar with the log paradigm.

Using JoinDomain credentials to execute other task sequences or scripts

0
0
I'm attempting to use the ZTIAddMember.wsf script to add the computer to security groups during MDT deployments.  Is there any way to execute this task sequence using the credentials used to join the domain (entered during the Deployment Wizard "Computer Details" step)?

Update rollup for Windows 7 SP1 and Server 2008 R2

0
0

Believe it or not, it has been released.

Check it out:
https://blogs.technet.microsoft.com/windowsitpro/2016/05/17/simplifying-updates-for-windows-7-and-8-1/

This convenience rollup package, available to download from http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3125574, contains all the security and non-security fixes released since the release of Windows 7 SP1 that are suitable for general distribution, up through April 2016.  Install this one update, and then you only need new updates released after April 2016.

Run OS Upgrade task sequence on McAfee Drive Encryption encrypted drive?

0
0

An OS Refresh task sequence on an encrypted drive can be done per this document:

https://kc.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/24000/PD24855/en_US/de_7_1_OS_refresh_guide_UEFI.pdf

However, I don't think McAfee support is yet familiar with the newer "Standard Client Upgrade" task sequence.

We need to upgrade our 10240 systems to 10586 without going through time consuming decrypt and re-encrypt processes.

Should changing the instructions in the document to simply inject the McAfee drivers into the base install.wim file and litetouch.wim files work and skip the steps on the last page (pasted below) since this is an in-place upgrade vs a "refresh?"

Has anyone had this work successfully?

• Mount EFI Partition
This is a command line option provided by Microsoft.
MountVol <Free Drive Letter:> /S (e.g. MountVol Y: /S)
• Replace MSBoot File - Part 1
This is a command line option that will recover McAfee Drive Encryptions EFI boot
program.
For 64‐bit systems use:
 xcopy y:\EFI\McAfee\Epe\MfeEEBoot.EFI y:\EFI\Boot\Bootx64.efi /y
For 32‐bit systems use:
xcopy y:\EFI\McAfee\Epe\MfeEEBoot.EFI y:\EFI\Boot\Bootia32.efi /y
• Replace MSBoot File - Part 2
This is a command line option that will recover McAfee Drive Encryptions EFI boot
program.
For 64‐bit systems use:
xcopy y:\EFI\McAfee\Epe\MfeEEBoot.EFI y:\EFI\Microsoft\Boot\Bootmgfw.efi /y
For 32‐bit systems use:
xcopy y:\EFI\McAfee\Epe\MfeEEBoot.EFI y:\EFI\Microsoft\Boot\Bootmgfw.efi /y



Viewing all 11297 articles
Browse latest View live




Latest Images