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

quick question about DB

$
0
0

Hi,

I am installing new MDT2013. Checked couple of installation guides. Some of them shows SQL Express installation checked, some not.

I never configured SQL on my current MDT2012.

I read about benefits of SQL on MDT server. But not planning to use at this time.

1. I believe that no SQL Express initially installed will not have any effect on initial Driver Groups, capture and deployment procedures. And I can install SQL later when will be ready (have more knowledge).

2. What is the relation between customsettings.ini and DB?

Thanks.


--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis


HIDESHELL=YES Causes "Dirty Environment Found" message when Windows boots for the first time

$
0
0

I have read several posts on this topic like http://social.technet.microsoft.com/Forums/en-US/mdt/thread/36ed037b-51b1-4053-a248-46bd3ac9ecda where the Dirty Environment Found message appears, but the circumstances are a bit different in my case. 

I have a new MDT 2012 Update 1 task sequence with a newly captured Windows 7 SP1 x86 image captured with MDT 2012 Update 1.

If I run the task sequence with no HIDESHELL specified in CustomSettings.ini, it runs to completion with no issues.  If I set HIDESHELL=YES in CustomSettings.ini, then the StateRestore phase starts with booting to Windows 7, auto-logging in and then the task sequence continues.  At the same time, I get the Dirty Environment Found message and if I leave it alone, the task sequences completes with no errors, just with the Dirty Environment FOund message on top.

This only happens when HIDESHELL=YES is specified in CustomSettings.ini.

MDT 2010 Deploy, DHCP Error

$
0
0

hi all

from time to time we I have with MDT deploy Windows 7.

Error: "A connection to the deployment share  could not be made. DHCP lease was not optained for any networking." START - cmd ipconfig show's a correct DHCP IP Address. There was a new Icon/Link "resume task sequence"  on Desktop. After I click "resume Task sequence" it works fine (without reboot, without modification)

DHCP lease time is 1 day. Workstation is fast and have SSD Drive. Is this a timing problem.

 


Chris

Setting "recommended" screen resolution automatically with MDT 2012?

$
0
0
I found some older posts on this, but nothing recent.  Is their an nice way we can set the, "recommended" screen resolution automatically? 

MDT 2010 A connection to the deployment share could not be made

$
0
0

Hi

I am getting this error when running lite touch deployment from WDS:

A connection to the deployment share (server name) could not be made. DHCP lease was not obtained for any networking device! Possible Cause: Check physical connection. Abort, Retry, Ignore.

I hit ignore and do an ipconfig and it states media disconnected but it had to have been connected to connect to WDS? It has no IP address yet the description lists the correct driver?

I have ran this same deployment on other hardware on the site without any issues and I have imported all the drivers into WDS and MDT, can you please advise?

Thanks

Jake

MDT 2010 - Connection to deployment share error, with network driver in WinPE

$
0
0
Hi all,

I am using MDT 2010 to deploy Windows 7 and I have an issue with network drivers in Windows PE.

I have a deployment share that allows me to create and capture a custom wim image and another deployment share to deploy that custom wim. When I use a windows PE image without network drivers (no need for optiplex 360 et latitude e5500), I can capture a wim or refresh a computer without errors.

Recently, I had to add a network drivers for Dell Optiplex 380 into PE (which is the same network driver as OP360 and E5500). With these drivers, I can boot my PE image from WDS and connect to my deployment shares without error.
I've got an error only when the computer need to reboot into winPE after the LTIApply task (capture or refresh). In this case, the connection to the deployment share could not be made and I receive an error. If I launch Litetouch.vbs manually from WinPE cmd prompt, the deployment continues to the end.

Here is the bdd.log error :
No physical adapters present, cannot deploy over wireless    LiteTouch    27/01/2010 16:53:25    0 (0x0000)
Unable to connect to \\computername\Deploy$.
DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection.    LiteTouch    27/01/2010 16:53:25    0 (0x0000)
FAILURE ( 5201 ): A connection to the deployment share (\\computername\Deploy$) could not be made.  The deployment will not proceed.    LiteTouch    27/01/2010 16:53:53    0 (0x0000)

It seems like an error in MDT 2008 when we needed to add a pause before launching wpeinit. But this bug is supposed to be fixed in MDT 2010.
This is weird because, with the same PE wim image with net drivers included, I can connect to my deployment share when I boot WinPE from WDS but I can't connect if I am coming from a full OS (capture or refresh).

I have the ztiutility script up to date : http://blogs.technet.com/msdeployment/archive/2009/09/18/fix-for-multiple-connections-to-a-server-or-shared-resource-by-the-same-user-using-more-than-one-user-name-are-not-allowed-problem-with-mdt-2010.aspx

If I remove the network drivers of PE images, the deployment works great (but I need them for OP380 Model).

Do you have any ideas about what is causing this issue ?

Thanks for your help.

Windows 8 activation through MDT

$
0
0

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?

How to Update MDT db.computerssettings table from stored procedure

$
0
0

HI , 

can someone please tell me the method to update the computersettings table from sql query, 

problem is my stored procedure updates the settings table but not computersettings table in mdt, i need to add value to OSDComputer name and query from csettings in ini, but since computersettings table is empty i am unable to get the value.

Thanks


Intelpcc.sys driver error on Dell Latitude E5450

$
0
0
Tried to deploy a Windows 7 x64 image via MDT to the Latitude E5450, but deployment would stop after the unattended .xml, when Windows loads for the first time, with a blue screen driver error for intelpcc.sys. This driver is for the Intel Collaborative Processor Performance Control driver. Drivers are up to date from Dell's cab site. I then tested deploying Windows 8.1 to the same machine, and the deployment was successful. Does anyone have a fix for Windows 7 and this driver issue? Thank you.

HP Pavilion Slimline

$
0
0
Just purchased a HP Pavilion Slimline 400-334 PC. I deployed windows 7 from MDT 2012. Image appeared to install correctly; however, upon reboot I get "windows starting" and nothing happens, just sits there. Any help would be appreciated. Maybe I need to run diskpart and re-format the drive. It appears maybe driver issue? Looking in the bios, storage, sata, options are sata or IDE. Tried both. 

question concerning variables in MDT's provider

$
0
0

I have a simple script that copies a file to a share that my creds have access to.  Using the run powershell command in MDT 2013 it fails with access denied.  Does the powershell command not run under my creds.

I've found some conversations regarding these variables, but I cannot seem to find concrete information on how they are used...

$tsenv:UserID
$tsenv:UserDomain
$tsenv:UserPassword

Deployment Blue Screens

$
0
0

Hi,

I'm trying to deploy a Windows 7 image to a Dell Optiplex 9010. The install process completes, but on the first reboot, results in a blue screen.

STOP: 0x0000007E (0xFFFFFFFF0000005, 0x0000000000000000, 0xFFFFF880035AF7E8, 0xFFFFF880035AF040)

No driver files is specified in the blue screen message, which disappears almost immediately as it is displayed. I booted into a Linux disk to try and see if there were minidump files on the hard drive but there weren't any. The BDD.log files says to reference a log file in X:\Windows, but I can't find that drive anywhere. I take it that drive is used while MDT is running. Since the blue screen happens after the first reboot, neither MDT nor Windows is running at that point. I don't know how else to access X:\. I took a wild guess that it was the video driver that was causing the problem and removed that from the driver store and updated/redeployed the image only to have the same results. I have the latest drivers from Dell's web-site (4/14/15). I am not sure what else I can try. Please help?

Thanks


Jason

How to Quickly Wipe MBR in WinPE?

$
0
0

As part of our imaging process we need to the wipe the MBR of all machines that have been encrypted.  If I boot a Win8.1 amd64 ISO, select Repair > Advanced > Command Prompt > Run bootrec.exe /fixmbr, it works fine and corrects the issue we encounter when we don't do this.

I copied what I thought were the necessary files into our amd64 winpe.wim, based on the following sites:

And although it appears to run successfully (no errors; it claims it executed successfully etc.) it doesn't seem to be doing anything as the problem persists.  

So: What files are required in order for bootrec to execute/function successfully in a WinPE environment?



If you're asking "What's the issue you're encountering?":
We use Symantec Encryption Desktop (aka PGP) and it adds a bootguard to the MBR.
We need to clear this out (wipe the MBR) in order for the machines to boot:

  • Creating a diskpart script to sel dis 0 and clean isn't sufficient to wipe the MBR

  • Converting the disk to GPT then back to MBR during a TS (prior to the format & partition step) will remove bootguard, HOWEVER, it causes the TS to fail once it gets into Windows with:
    "Wizard Error: Unable to find the SMS Task Sequencer.  The deployment will not proceed."

    I've tried doing this both via a task sequence step that runs a diskpart script (prior to the format & partition step) and by adding 'oUtility.RunCommandWrite oExec, "CONVERT GPT NOERR"' to around line 340 of ZTIDiskPart but the results are the same.

  • Uninstrumenting the drive should correct this, but you cannot uninstrument an encrypted disk and decrypting the drive takes way too long

  • Secure wiping the disk (e.g.: via WipeDisk, DBAN) takes way too long

I'm open to using third-party utilities, but would prefer something I can use in WinPE during the Task Sequence.


8.1 Post OS Task Sequence stops after reboot (MDT 2013)

$
0
0

We are trying to run Post OS task sequence on a basic Windows 8.1 image (logged in as local admin with no password) to do several things.  Some reboots are needed but the task sequence stops after the reboots.  We have discovered several things:

- we see that a shortcut to run litetouch.wsf is put in the startup folder before the reboot but it does not seem to launch when coming back in to Windows because I assume startup items are prevented from running in admin mode in Windows 8.1

- We can get the task sequence to continue if we open a elevated command prompt and run C:\MININT\Scripts\litetouch.wsf

- This same task sequence runs without stopping on a Windows 7 machine.

- Turning of UAC does not make a difference

Anyone run in to this?  When running a full Client task sequence that installs the Windows 8.1 OS MDT does not seem to have an issue with the reboots.  What does it do differently there that it does not do in the "Post OS" task sequence?

Thanks!

BitLocker Recovery key is not created when added bitlocker recovery command in the MDT task sequence

$
0
0

Hi,

I am trying to enable bit locker in client machine through MDT task sequence. In client machine every thing work fine and also operating system is encrypting but problem is that no recovery key is created in AD. to check weather there is any issue in the command i manually type the same command which i used in the MDT TS in the command prompt and this time key is created in the AD. I don't know why the same command not creating key in AD and encrypting the device.

i used following command in the MDT TS


Guidance on Post OS Task Sequence on Windows 8.1 with reboots?

$
0
0

Hello,

We are trying to come up with a deployment solution for our Surface Pro devices, and would like to utilize the Post OS task sequence templates in MDT 2013.

We have plenty of experience with bare metal deployments, but none with these Post OS task sequences, and there are a few questions we have.

  1. MDT is designed to be used with the built in Administrator account. This appears to be disabled in Windows 8.1. Do we just re-enable it so MDT will work?
  2. Along those same lines, we noticed that if the task sequence reboots (because of a Recover from Domain step), it will not auto login as Administrator and finish the task sequence. Do we have to make the Administrator account auto login ourselves via a script or something?

What is the "right way" to run these Post OS Task Sequences on Windows 8.1? Specifically to run a domain join and resume after reboot?

Thanks!

MDT 2013 Keyboard and Mouse Are Not Working

$
0
0

I'm trying to image a computer, but one I boot the computer to MDT the keyboard and mouse stop working. They working fine in safe mode and BIOS.

Not sure where I can add the drivers for them in the task sequence.

Please help!

WinPE can't find USB offline deployment share

$
0
0

I believe this is because the USB driver WinPE wants is missing.  This is for Windows 7 64-bit.

If I install "all drivers," in the WinPE selection profile, it finds the deployment share on the USB media, installs the OS and then blue screens during Windows Plug and Play.

If I try to limit the drivers to only storage, Ethernet and USB, then it prompts for the path to the deployment share.

I have tried the USB specific driver and I have tried all chipset drivers.

http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=5212910&swItemId=ob_135422_1&swEnvOid=4059

How can I find which driver MDT is looking for to run USB offline deployment?




Unable to deply image on Soild State Drive MDT 2012 update1

$
0
0

I am trying to deploy a laptop with  solid-state drive during diskpart it is not able to format the drive. Looking at the log file I am seeing this Waiting for Drive to Exist with a % number. When we got the drive fresh from the Vendor we were able to install windows with out an a problem now that we are doing it again on the same drive it is not working. I have formated the drive and have set is as active but that still does not seem to make it work. Any ideas would be helpful.

Stuck after first reboot

$
0
0

I can successfully deploy my Windows7 x64 image to a VM using MDT2013. So, the next phase of my setup was to start injecting drivers into my Task Sequence based on hardware model in our organisation (Win7\%make%\%model%)

After the Inject Drivers/Restart tasks execute (was really quick), the PC reboots and sits at the Windows 7 login screen (can't login). As from the above screenshot, I have temporarily disabledDriverGroup001 but this hasn't helped. Any advice?

Viewing all 11297 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>