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

Language of Modern Apps changed after Deployment

November 22, 2013, 10:06 pm
$
0
0

Hi,

after deploying a Windows 8.1 Pro Image with MDT 2013 all the in-built apps have their language changed for all users. Before i do a Capture and Sysprep Task Sequence i can see that all the apps are in the "native" language (german) but when i take the captured .WIM and do a standard deployment task sequence with it, the language of all the apps change to english - and i haven't find a way to revert this yet.

so how can i prevent this language change that happens during deployment or how can i revert it afterwards? the other regional settings are fine and are correctly set as specified in the deployment properties - it's only the modern apps that are wrong...

thanks!

↧
Search

New Win7 32bit via MDT

November 25, 2013, 7:22 pm
$
0
0

Hi,

Thanks for reading my post.

We are using MDT 2010 for deploying Windows 7 64bit now.

Due to compatibility issue we need to add Windows 7 32 bit into MDT 2010.

Could anybody tell me what's the best practice for our task?

Any idea will be appreciated.

Thanks in advance.

Rowen

↧
↧

Deployment Wizard Script Error.

November 26, 2013, 12:53 am
$
0
0

Hi,

Over the weekend an error has occurred in my Deployment Wizard.

When the deployment-process is started, even  before the Task Sequence selection, the Wizard stops with a Script Error.

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

Error One:

Line: 212
Char: 4
Error: Input past end of file
Code: 0
URL: file:///I:/deploymentshare/Scripts/Wizard.hta

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

Error two:

Line: 321
Char: 4
Error: Object required: 'oElement'
Code: 0
URL: file:///I:/deploymentshare/Scripts/Wizard.hta

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

Any bright minds that can point me in the right troubleshooting direction?

-Stephan

↧

Deploying Custom Windows 8.1 Custom Image using MDT 2013

November 26, 2013, 1:37 am
↧

Find product key in unattend.txt and paste it to DeployWiz. Script.

November 26, 2013, 3:04 am
$
0
0

Scenario: I am using MDT 2010u1 for deploying Windows XP and Windows 7 on target. I want to deploy Windows XP with specifiedin task sequence product key (global variables ProductKey, OverrideProductKey and SkipProductKey are not set). Specified in task sequence key usually stored in unattend.txt and sysprep.inf in %DS%\Control\%TS_ID%. But MDT does not paste a key in "Product key" text area in Deployment Wizard. Even if it specified in unattend answer file. I cannot continue a deploy OS configuration process with empty "Product key" text area. I made a few changes in two MDT script files to add this functionality.

I can share scripts. Are they may be useful for community?






↧
↧

MDT: a supported prevois version of windows was not found. I'm trying to deploy windows 7 image to a windows xp client.

November 26, 2013, 8:24 am
$
0
0

The "move the user data and settings" option is greyed out. I then get the following error in litetouch pe screen

"A supported previous version of windows was not found. "

I'm trying to deploy windows 7 image to a windows xp client.

how do i save the user data before deploying windows 7 to it?

Anand_N

↧

MDT Refresh Failure 5624

November 26, 2013, 9:15 am
↧

MDT 2012 USMT MigApp.xml replaces with original

November 25, 2013, 12:01 pm
$
0
0

This should be an easy one.

I'm using MDT 2012 update 1 with USMT 5.0

I modified the deployment share Tools\arch\USMT5\MigApp.xml

After updating the deployment share and creating media, I notice the XML file is reverted back to the default MigApp.xml file, losing my customization.

Is this default behavior? Can this be avoided any other way than creating separate XML files and adding items to CustomSettings?

↧
Search

Dart 8.0 and Server 2012 R2

November 25, 2013, 5:09 pm
$
0
0

Hi!

I am using MDT 2013 on Server 2012 R2 and Dart 8.0 won't install (trying to integrate Dart tools to MDT build).

http://technet.microsoft.com/en-us/library/jj680675.aspx

I see 2012 as an accepted platform, but R2 doesn't work? Can anyone offer me any insight as to a work around?

Thanks!

↧
↧

Which Windows PE?

November 26, 2013, 10:40 am
$
0
0

I'm having so many problems deploying Windows 8.1 with MDT 2013 that I need to go back to the absolute basics to make sure I haven't done smthng stupid...

Which Windows PE version should I be using for deploying Windows 8.1 Enterprise x64 with MDT 2013?

How do I tell which version I am using right now?

Is there a consolidated list of which PE versions can be used to deploy various OS's?

--smthng

↧

Not seeing WIM in Operating systems in MDT

March 3, 2013, 8:57 pm
$
0
0

Hi,

I have imported custom WIM (Already existing and created through sccm earlier) in MDT 2012 but unfortunately it doesn't appear in MDT console  under operating systems..pls. find the screen attached. Any idea what could be the reason. Currently I have integration of SCCM and MDT 2012. 

Regards,

↧

MDT 2013 Hangs at Cleaning Drive and 100% Applying Image

November 12, 2013, 12:56 pm
$
0
0

Dealing with a strange issue with MDT 2013. Our task sequences (all of them, doesn't matter if it's 2008 R2, 2012, or 2012 R2) seem to be randomly hanging at the Cleaning Drive or after getting to 100% Applying Image phase - no errors. If I open a command prompt before starting, then run a task sequence, when it gets to that part where it hangs, if I run diskpart it'll immediately continue. Don't have to enter any commands, just have to run diskpart. The logs don't show any errors - for instance, on one where it hung at 100% applying image:

<![LOG[Return code from command = 0]LOG]!><time="11:04:24.000+000" date="11-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Find the boot drive (if any) [True] [6.1.7601.17514] [False]]LOG]!><time="11:04:24.000+000" date="11-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">

Nothing after that - as soon as I run diskpart, the deployment will continue. I've tried this on several different Dell PowerEdge systems (M600, 1955, R710) and see the same random behavior. It happens about 50% of the time. I tried adding the latest PERC driver, and also tried disabling the PERC drivers entirely so it would just use in-box drivers with the same result. This was a MDT 2012 U1 installation that was upgraded to MDT 2013. Note that this does not happen when deploying to VMware virtual machines, only physical systems.

I'm at a loss ...

Jeff Graves, ORCS Web, Inc.

↧

Drivers no longer installing properly

November 25, 2013, 12:22 pm
$
0
0

Hi,

Recently my deployment has broken, with drivers not being installed properly, including network, which stops the whole deployment on first boot.  It had been working fine up until a week or two ago, and I'm not sure what changed (or maybe I changed something...)

Anyways, I'm using selection profiles to choose the drivers for the particular hardware Windows 7 is being deployed to, and during the Task Sequence I can see the correct hardware being chosen and drivers supposedly being copied.  It then installs the OS and reboots, but when it logs into Windows for the first time the drivers are missing.

This is broken across all of our different hardware models, so it's not just one set of drivers that broke as far as I can tell.

Where can I look to figure out what is going wrong with the driver injection?

Thank you.

↧
↧

MDT 2012 - Suddenly Not Functioning Correctly.

November 26, 2013, 1:18 pm
$
0
0

I have a MDT 2012 deployment share I've used since Win7 came out and upgraded as needed.

I've been using it for development of driver collections, and WIM development.

I had a new model laptop come in and when I went to image it, it squacked in WinPE that the NIC driver wasn't available.

I checked and the correct INF was in my Out of Box repository.  I ended up downloading the current Dell Driver, and Intel drivers in both x86 and x64.  Rebuilt the boot dir from scratch each time.  Each time I would get the error, each time I'd confirm the DISM log had included the driver in the PE.  Each time I'd match the HWID's from the error and the DISM log and PE.  Still the computer wouldn't boot.

I decided to try to image it from within windows with LiteTouch.  Win7x64 Task Sequence started as normal except after all the validation steps it suddenly ends with "Successfully Completed."

I tried to capture an image from an older WinXP machine.  Same thing, "Successfully Completed" after validation steps.

Tried to boot PE on an older desktop machine and load a Win7x86 wim.  Installed fine with no errors.

Tried to boot PE on an older desktop machine and load a Win7x64 wim.  Installed fine with no errors.

Tried to boot PE on an older laptop machine and load an x64 Win7 wim.  Installed, but when up to the "System is applying system settings"  boot screen I got an error of "Install Windows - Windows could not configure one or more system components.  To install Windows, restart the computer and then restart the installation."

Tried on another laptop I know the x64 WIM and driver set works on, and got the same error.

On the same laptop machine I tried to load the Win7x86 wim from BootPE.  It loaded fine without error.

I've check every log I can think of and can't find an error documented in any of them.

I created a new customsettings.ini and made it as generic as possible, and still it skipped.

I removed everything from the customersettings.ini and used the wizard and still it completed without loading the image.

Can someone point me in a direction?  Is there a log I'm overlooking?

There's no place like 127.0.0.1

↧

Cannot import image under new 2013 WDS

November 26, 2013, 10:41 am
$
0
0

Hello there.

recently, we installed the new deployment workbench 2013 Version: 6.2.5019.0

I just recently tried to create an XP image, the same way as I always do. I had the file captured to the /capture directory. I then tried to do an operating system import, again that I have done a thousand times. I select move the wim file and give it a new name. The task goes through to completion with no errors. The physical WIM file is moved, however 2 things do not happen. Firstly, it does not show up in deployment workbench. The second is that in the directory, the file 'lang.ini' has not been created.

I tried to move a lang.ini from another older XP image directory but it hasnt made a difference. Tried doing this Workbench import from two different machines. Cannot import my custom WIM file with the new version. It does not show up under "operating systems" or any of the sub directories.

Anyone else seeing this problem?



↧
Search

Bit Locker Recovery/MDT 2013 store in AD Windows 8.1 Issues!

November 26, 2013, 2:52 pm
$
0
0

I am building Win8.1 Enterprise with MDT 2013 and am attempting to store the recovery information as a child object of the host laptop object on a WS2008 R2 AD DS environment.

I have told the machine via GPO to store recovery key in AD and have verified this policy was applied to the new machine. When I open up the manage bit locker GUI, it lets me type in an 8-20 character PIN but doesn't have the screen that says where to store the key (USB, Locally, Store in Active Directory etc). 

I enter in a PIN and reboot the machine. Then in order to get the recovery key to store as the child object of "LAPTOP-TEST" (machine host name), I have to run an elevated command prompt and run:

manage-bde.exe -protectors -get c: which spits out the numerical ID

then

manage-bde.exe -protectors -adbackup c: -id {IDHERE} which successfully adds the recovery information to the object in AD.

Is there a way to tell the bit locker set-up that I am going to store the recovery key in ADbefore the encryption process has started? Additionally, this powershell script seems like it should do the steps above automatically but closes the shell window before I can read if it executed correctly. 

Option Explicit

    Dim strNumericalKeyID
    Dim strManageBDE,strManageBDE2
    Dim oShell
    Dim StrPath
    Dim StdOut, strCommand
    Dim Result, TPM, strLine
    Dim Flag, NumericalKeyID

    Set oShell = CreateObject("WSCript.Shell")

    '====================================================================================
    'This section looks for the Bitlocker Key Numerical ID

    strManageBDE = "Manage-BDE.exe -protectors -get c:" 'Bitlocker command to gather the ID

    Flag = False

    Set Result = oShell.Exec(strManageBDE)'sees the results and places it in Result

    Set TPM = Result.StdOut    'Sets the variable TPM to the output if the strManageBDe command

    While Not TPM.AtEndOfStream
       strLine = TPM.ReadLine  'Sets strLine
       If InStr(strLine, "Numerical Password:") Then  ' This section looks for the Numerical Password
        Flag = True
       End If
       If Flag = True Then
         If InStr(strLine, "ID:") Then  'This section looks for the ID
          NumericalKeyID = Trim(strLine)' This section trims the empty spaces from the ID {} line
          NumericalKeyID = Right(NumericalKeyID, Len(NumericalKeyID)-4)
          Flag = False 'Stops the other lines from being collected
         End If
       End If
    Wend

strManageBDE2 = "Manage-BDE.exe -protectors -adbackup C: -ID " & NumericalKeyID
oShell.Run strManageBDE2, 0, True 'Runs the Manage-bde command to move the numerical ID to AD.


I checked the local machines registry - all registry dwords are set to value "1" needed for storing recovery key in AD.

As of now, I don't want to have to manually run these commands on each machine after deploying a windows 8.1 build.

Here is my customsettings.ini

[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
HideShell=NO
ApplicationSuccessCodes=0 1 2 1060 3010
Applications001={b7d20a21-434c-4921-b0cd-85f69e0aa4d0}
Applications002={d3abef28-3240-420b-ab22-bed8f03e4565}
SkipAppsOnUpgrade=YES
SkipPackageDisplay=YES
SkipAdminAccounts=NO
SkipComputerName=NO
SkipDomainMembership=NO
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=NO
SkipSummary=NO
SkipBDDWelcome=YES
SkipFinalSummary=YES
TimeZone=004
TimeZoneName=Pacific Standard Time
Home_page=
FinishAction=SHUTDOWN
DoNotCreateExtraPartition=NO
BDEDriveLetter=S:
BDEDriveSize= 2000
BDEInstall=ProtectKeyWithTpm
BDERecoveryKey=AD
BDERecoveryPassword=TRUE
BDERequired=YES
OSDBitLockerCreateRecoveryPassword=TRUE

↧

Use VMWare for refrence Image?

November 26, 2013, 1:17 pm
$
0
0
Ok so what I want to do is create a universal image to deploy to multiple lenovo desktops. Can I install windows 7 in a vm plus all my applications then create a task sequence in mdt to sysprep and capture the vm then import it into mdt and deploy that to the desktops without any issues?
↧
↧

Bitlocker:

January 31, 2013, 6:54 am
$
0
0

Here's what I get:

BDD.log:

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

We are running a OS that supports BitLocker ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
OSDBitLockerTargetDrive= , OSDBdeTargetDriveLetter= , sOSDBitLockerTargetDrive= C:ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
About to perform variable rationalization.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
BitLocker Mode set to: TPMZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Starting search for removable driveZTIBde1/30/2013 5:40:51 PM0 (0x0000)
The search for a USB drive failedZTIBde1/30/2013 5:40:51 PM0 (0x0000)
BitLocker Startup Key Drive Value set to: C: ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
BitLocker Create Recovery P@ssword Status: AD ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
BitLocker Wait For Encryption Status set to: TRUE ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
BitLocker Recovery P@ssword set.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
The current autorun setting is - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Disabling AutorunZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Find the boot drive (if any) [False] [0.0.0.0] [False]ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDisk : \\CNU250CPCP\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
No boot drives found. None.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Reverting autorun setting to - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Setting BDE Drive letter to nothing as we are unable to get the boot drive.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Property BdeDriveLetter is now = ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Running first pass..ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDisk : \\CNU250CPCP\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
   Partition Count: 2ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
ZTIDiskUtility!GetDiskFreeSpace should be deprecated, does not handle avaible space for a new partitionZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDisk : \\CNU250CPCP\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
GetPartitions: 2ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDiskPartition : \\CNU250CPCP\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\CNU250CPCP\root\cimv2:Win32_LogicalDisk.DeviceID="C:"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
   Free Disk Space: 0ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Existing Bitlocker: ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
The current autorun setting is - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Disabling AutorunZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Find the boot drive (if any) [False] [0.0.0.0] [False]ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDisk : \\CNU250CPCP\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
No boot drives found. None.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Reverting autorun setting to - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Existing Boot Drive: 1ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
The current autorun setting is - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Disabling AutorunZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Find the boot drive (if any) [False] [0.0.0.0] [False]ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDisk : \\CNU250CPCP\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
No boot drives found. None.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Reverting autorun setting to - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Windows has a hidden system partition, no disk actions are necessaryZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Configuring protectors.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Success TPM EnabledZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Success TPM Is ActivatedZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Success TPM Is OwnedZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Success TPM Ownership AllowedZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Check for Ensorsement Key Pair Present = 0ZTIBde1/30/2013 5:40:52 PM0 (0x0000)
TpmEnabled: TrueZTIBde1/30/2013 5:40:52 PM0 (0x0000)
TpmActivated: TrueZTIBde1/30/2013 5:40:52 PM0 (0x0000)
TpmOwned: TrueZTIBde1/30/2013 5:40:52 PM0 (0x0000)
TpmOwnershipAllowed: TrueZTIBde1/30/2013 5:40:52 PM0 (0x0000)
EndorsementKeyPairPresent: TrueZTIBde1/30/2013 5:40:52 PM0 (0x0000)
TPM Validation CompleteZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Encryptable Volume Count:1ZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Attempting to bind to: C:ZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Success setting oBdeVol ZTIBde1/30/2013 5:40:52 PM0 (0x0000)
BDE Instance Bind CompleteZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Performing ProtectKeyWithTpm InstallationZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Attempting to enable BitLocker TPMZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Recovery P@ssword being saved to C:\CNU250CPCP-{CAD42C6E-2450-4F6C-AC91-CC57718FDF5D}.txtZTIBde1/30/2013 5:40:54 PM0 (0x0000)
Attempting to intiate ProtectKeyWithNumericalP@sswordZTIBde1/30/2013 5:40:54 PM0 (0x0000)
<Message containing password has been suppressed>ZTIBde1/30/2013 5:40:54 PM0 (0x0000)
<Message containing password has been suppressed>ZTIBde1/30/2013 5:40:54 PM0 (0x0000)
Property restore is now = ZTIUserState1/30/2013 5:40:55 PM0 (0x0000)

ZTIBDE.log:

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

Microsoft Deployment Toolkit version: 6.1.2373.0 ZTIBDE1/30/2013 5:19:53 PM0 (0x0000)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.ZTIBDE1/30/2013 5:19:53 PM0 (0x0000)
System drive is: X:ZTIBDE1/30/2013 5:19:53 PM0 (0x0000)
The deployment method is not using ConfigMgr. ZTIBDE1/30/2013 5:19:53 PM0 (0x0000)
We are in a Windows PE environment, checking to see if Windows PE supports Offline BitLocker tasks.ZTIBDE1/30/2013 5:19:53 PM0 (0x0000)
Determining if WinPE supports pre-provisioning ZTIBDE1/30/2013 5:19:53 PM0 (0x0000)
Found Offline BitLocker Tools.ZTIBDE1/30/2013 5:19:53 PM0 (0x0000)
Checking to see if OS supports Offline Bitlocker. ZTIBDE1/30/2013 5:19:53 PM0 (0x0000)
OS build supports Offline BitLocker.ZTIBDE1/30/2013 5:19:53 PM0 (0x0000)
Success TPM EnabledZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
Success TPM Is ActivatedZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
Success TPM Is OwnedZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
Success TPM Ownership AllowedZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
Check for Ensorsement Key Pair Present = 0ZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
TpmEnabled: TrueZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
TpmActivated: TrueZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
TpmOwned: TrueZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
TpmOwnershipAllowed: TrueZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
EndorsementKeyPairPresent: TrueZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
TPM is validated.ZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
OSDTargetDriveCache was determined earlier : C: ZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
Property OSDTargetDriveCache is now = C:ZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
Property OSDisk is now = C:ZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
Pre-provisioning BitLocker on drive C:ZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
OSDTargetDriveCache was determined earlier : C: ZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
Property OSDTargetDriveCache is now = C:ZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
Property OSDisk is now = C:ZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
About to run command: "X:\WINDOWS\system32\Manage-bde.exe" -on C: -usedZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
Command has been started (process ID 1232)ZTIBDE1/30/2013 5:19:54 PM0 (0x0000)
ZTI Heartbeat: command has been running for 0 minutes (process ID 1232)ZTIBDE1/30/2013 5:19:55 PM0 (0x0000)
Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 1232)ZTIBDE1/30/2013 5:19:55 PM0 (0x0000)
Return code from command = 0ZTIBDE1/30/2013 5:19:55 PM0 (0x0000)
Property IsBDEPreProvisioned is now = TrueZTIBDE1/30/2013 5:19:55 PM0 (0x0000)
ZTIBDE processing completed successfully.ZTIBDE1/30/2013 5:19:55 PM0 (0x0000)
Event 41001 sent: ZTIBDE processing completed successfully.ZTIBDE1/30/2013 5:19:55 PM0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
System drive is: C:ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
The deployment method is not using ConfigMgr. ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
This script is not currently running in Windows PE ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
We are running a OS that supports BitLocker ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
OSDBitLockerTargetDrive= , OSDBdeTargetDriveLetter= , sOSDBitLockerTargetDrive= C:ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
About to perform variable rationalization.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
BitLocker Mode set to: TPMZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Starting search for removable driveZTIBde1/30/2013 5:40:51 PM0 (0x0000)
The search for a USB drive failedZTIBde1/30/2013 5:40:51 PM0 (0x0000)
BitLocker Startup Key Drive Value set to: C: ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
BitLocker Create Recovery P@ssword Status: AD ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
BitLocker Wait For Encryption Status set to: TRUE ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
BitLocker Recovery P@ssword set.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
The current autorun setting is - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Disabling AutorunZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Find the boot drive (if any) [False] [0.0.0.0] [False]ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDisk : \\CNU250CPCP\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
No boot drives found. None.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Reverting autorun setting to - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Setting BDE Drive letter to nothing as we are unable to get the boot drive.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Property BdeDriveLetter is now = ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Running first pass..ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDisk : \\CNU250CPCP\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
   Partition Count: 2ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
ZTIDiskUtility!GetDiskFreeSpace should be deprecated, does not handle avaible space for a new partitionZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDisk : \\CNU250CPCP\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
GetPartitions: 2ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDiskPartition : \\CNU250CPCP\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\CNU250CPCP\root\cimv2:Win32_LogicalDisk.DeviceID="C:"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
   Free Disk Space: 0ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Existing Bitlocker: ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
The current autorun setting is - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Disabling AutorunZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Find the boot drive (if any) [False] [0.0.0.0] [False]ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDisk : \\CNU250CPCP\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
No boot drives found. None.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Reverting autorun setting to - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Existing Boot Drive: 1ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
The current autorun setting is - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Disabling AutorunZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Find the boot drive (if any) [False] [0.0.0.0] [False]ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
New ZTIDisk : \\CNU250CPCP\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
No boot drives found. None.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Reverting autorun setting to - 145ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Windows has a hidden system partition, no disk actions are necessaryZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Configuring protectors.ZTIBde1/30/2013 5:40:51 PM0 (0x0000)
Success TPM EnabledZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Success TPM Is ActivatedZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Success TPM Is OwnedZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Success TPM Ownership AllowedZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Check for Ensorsement Key Pair Present = 0ZTIBde1/30/2013 5:40:52 PM0 (0x0000)
TpmEnabled: TrueZTIBde1/30/2013 5:40:52 PM0 (0x0000)
TpmActivated: TrueZTIBde1/30/2013 5:40:52 PM0 (0x0000)
TpmOwned: TrueZTIBde1/30/2013 5:40:52 PM0 (0x0000)
TpmOwnershipAllowed: TrueZTIBde1/30/2013 5:40:52 PM0 (0x0000)
EndorsementKeyPairPresent: TrueZTIBde1/30/2013 5:40:52 PM0 (0x0000)
TPM Validation CompleteZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Encryptable Volume Count:1ZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Attempting to bind to: C:ZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Success setting oBdeVol ZTIBde1/30/2013 5:40:52 PM0 (0x0000)
BDE Instance Bind CompleteZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Performing ProtectKeyWithTpm InstallationZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Attempting to enable BitLocker TPMZTIBde1/30/2013 5:40:52 PM0 (0x0000)
Recovery P@ssword being saved to C:\CNU250CPCP-{CAD42C6E-2450-4F6C-AC91-CC57718FDF5D}.txtZTIBde1/30/2013 5:40:54 PM0 (0x0000)
Attempting to intiate ProtectKeyWithNumericalP@sswordZTIBde1/30/2013 5:40:54 PM0 (0x0000)
<Message containing password has been suppressed>ZTIBde1/30/2013 5:40:54 PM0 (0x0000)
<Message containing password has been suppressed>ZTIBde1/30/2013 5:40:54 PM0 (0x0000)

Bitlocker goes into suspend mode. Why Key is not stored in AD?

Thanks

↧

USMT Printer 'Update Driver' in 32 -> 64bit deployments

November 25, 2013, 8:53 pm
$
0
0

When doing 32 bit Windows XP to 64 Bit Windows 7,  USMT is migrating all the network printers, which is great.  As the drivers are obviously not correct though, the driver needs to be manually upgrade (right click printer --> Update Driver).

Is there any way to script this action?  I cant seem to find any documentation on it!

As our USMT task sequence is separate from the deployment and runs under the migrated user's context I'm sure it would work. If I could just get the right syntax, add a Powershell script at the end of the TS that would be perfect!

↧

Can't remote in machine deployed using MDT 2012?

November 25, 2013, 12:42 am
$
0
0

So after i've deployed windows 7 pro (Machine A) from MDT 2012 , and wanted to remote in via RDP. However i can't seem to remote in, even after enabling Remote Desktop , disabling windows firewall  and ensuring local GPO allows RDP.

After hours of googling, i realize that the default GPO deployed by MDT 2012 introduces a registry "LMcompatibilityLevel"
with the value of 5. ( I checked on machines installed via ISO media, this registry doesn't even exist)

From here ,http://technet.microsoft.com/en-us/library/cc960646.aspx
I understand its all about the authentication protocol (though i don't really understand much about it), and my machine
(domain machine) has a value of 1 for "LMcompatibilityLevel" registry. So i changed the key value on Machine A from 5 to 1, and now i can remote into the machine.

So my question is, is there a way to modify the default GPO package specifically on that value during deployment?

Or should i disable it?

Whats the importance of this registry key? It'd be good anyone could guide me on this matter.

Thanks a bunch!

↧
Viewing all 11297 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>