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

MDT 2012 Image Capture Warning: Failure: -1073741819 since moving capture VM to a new VM Host machine

March 23, 2015, 7:29 am
$
0
0

Hi,

I have a Windows 7 VM master that I capture a custom image from using MDT 2012 to deploy around my site. I have moved this VM to a different VMware Workstation host (new laptop) and now it gives a the following Warning when capturing:

Failure: - 1073741819 0xC0000005: Running MSHTA.exe "\\STC-ITD\Deploymentshare$\Scripts\Wizard.hta" /definition:DeployWiz_Definition_ENU.xml

I have made no changes to the VM master image other than move it from the previous machine running VMware Workstation to my new laptop running exactly the same version of VMware Workstation (10.0.4)

When the VM boots the first time on the new VMware Workstation it does reboot immediately, so I suspect that Windows detects some hardware changes that cause this, but I am not sure what should be so different as surely all the devices that Windows sees are VMware virtual ones which should be the same on both installations of VMware Workstation.

This is the only thing that has changed so I can only presume that this must be something to do with the warning in MDT when I try and capture the image.

I can find no answers to this issue anywhere - can anyone please help?

Thanks and Regards

Gary

↧
Search

MDT 2013 Windows 8.1 Task sequence Stops After first Reboot. login

May 12, 2014, 10:01 am
$
0
0

Hi There,

The issue I am having is that After the OS gets laid down, and the Windows 8.1 computer reboots, The task sequence does not continue. It fails everytime. There are not any obvious errors that happen in the process that I can see in the logs. But I have customized this process quite a bit and I could use some help. We are deploying potentionally to over 30,000 computers.

The test machine I have been using is the Surface pro 2.

The interesting part is after a failure is if I start the process over again ,  boots into PE, then run diskpart manually from command prompt to Clean Disk 0, and then reboot and start the MDT task sequence, it will deploy fine.

I also have a custom step that copies the TS media from the stick to a Recovery partition I create. The user can launch a -re-image or MDT refresh from an Icon/script, which will unhide this "recovery partition", and kick off a lite touch refresh. This works succesfully everytime. We have remote locations with very slow links, so MDT over the network or MDT integrated with SCCM is not an option at this time. So this is the solution.

I am attempting to use MDT 2013 to deploy Windows 8.1 Offline, and using GPT partitions.

I am using a custom Format and partiition Step, that call the CustomDiskpart.txt script from %deployroot%\Scripts.

I am also using a Split image, as multi partitioned EFI/NTFS USB sticks are not a possibility for us , also, the USB sticks capable of this are seen by MDT as a "fixed drive" anyways. Which can cause issues in itself. So the LTIAPPLY.wsf has been edited to search and apply ther split .swm files.  This works well.

After the Task sequence failure I have tried launching the Litetouch scripts from the C:\MINNINT folder manually to continue the sequence, but it doesnt  do anything.

I don't want to always be running Diskpart manually before imaging a new OEM computer. I needa second pair of eyes on this.

Thank You in advance!


↧
↧

Trying to use a task sequence to add a computer to a security group

March 24, 2015, 9:32 am
$
0
0

I am using the following code to try to add a security group to a computer account when I am imaging using MDT 2012.  I get the following errors after the imaging process has completed.  

Any help would be greatly appreciated.

Thanks,

Andy

Exception calling "InvokeMember" with "5" argument(s): "Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))"TaskSequencePSHost03/24/2015 8:45:29 AM0 (0x0000)
At \\AOTWDS01V\DeploymentShare$\Scripts\dagroup.ps1:26 char:2
+     $UserDN = $SysInfo.GetType().InvokeMember("ComputerName", "GetProperty", $Null, ...
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~TaskSequencePSHost03/24/2015 8:45:29 AM0 (0x0000)
NotSpecified: (:) [], MethodInvocationException TaskSequencePSHost03/24/2015 8:45:29 AM0 (0x0000)
The following exception occurred while retrieving member "Get": "The specified domain either does not exist or could not be contacted.
"TaskSequencePSHost03/24/2015 8:45:31 AM0 (0x0000)
At \\AOTWDS01V\DeploymentShare$\Scripts\dagroup.ps1:30 char:2
+     $strDomainPath = $ORoot.Get("defaultNamingContext")
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~TaskSequencePSHost03/24/2015 8:45:31 AM0 (0x0000)
NotSpecified: (:) [], ExtendedTypeSystemException TaskSequencePSHost03/24/2015 8:45:31 AM0 (0x0000)
Exception calling "Execute" with "1" argument(s): "An invalid directory pathname was passed
"TaskSequencePSHost03/24/2015 8:45:32 AM0 (0x0000)
At \\AOTWDS01V\DeploymentShare$\Scripts\dagroup.ps1:38 char:3
+         $oRs = $oConnection.Execute("SELECT adspath FROM 'LDAP://$strDomainPath' WHERE ...
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~TaskSequencePSHost03/24/2015 8:45:32 AM0 (0x0000)
NotSpecified: (:) [], MethodInvocationException TaskSequencePSHost03/24/2015 8:45:32 AM0 (0x0000)

Param(
[string[]]$GroupNames,
[String]$Admin,
[String]$Password
)
if($GroupNames)
{
[int] $ADS_PROPERTY_APPEND = 3
#Get the computer DN
$SysInfo = New-Object -ComObject "ADSystemInfo"
$UserDN = $SysInfo.GetType().InvokeMember("ComputerName", "GetProperty", $Null, $SysInfo, $Null)
$ComputerDN = "LDAP://$UserDN"
#Get the Domain DN
$ORoot = [ADSI]"LDAP://rootDSE"
$strDomainPath = $ORoot.Get("defaultNamingContext")
#Create ADODB connection
$oConnection = New-Object -ComObject "ADODB.Connection"
$oConnection.Provider= "ADsDSOObject"
$oConnection.Open("Active Directory Provider")
foreach($groupname in $GroupNames)
{
#Get the specefied group
$oRs = $oConnection.Execute("SELECT adspath FROM 'LDAP://$strDomainPath' WHERE objectCategory='group' AND  Name='$groupname'")
If (!$oRs.EOF)
{
$strAdsPath = ($oRs.Fields |  Select value ).value
}
If($strAdsPath)
{
If($Admin -and $Password)
{
$objGroup = New-Object DirectoryServices.DirectoryEntry($strAdsPath,$Admin,$Password)
}
Else
{
$objGroup = [ADSI]$strAdsPath
}
$objComputer = [ADSI]$ComputerDN
#verify if the computer is a member of the Group
If ($objGroup.ismember($objComputer.adspath) -eq $false) 
{
#Add the the computer to the specefied group
$objGroup.PutEx($ADS_PROPERTY_APPEND,"member",@("$UserDN"))
$objGroup.setinfo()
}
}
}
}

↧

Daylight savings time in WinPE

March 24, 2015, 9:45 am
$
0
0

In our MDT environment, we are collecting a lot of data about the deployments and putting them into SQL for reporting. One of the things we are interested in is how long the deployments take.

In the beginning of the task sequence, we have a Powershell script that gets the current time and puts it into a variable called 'deployStartTime'. At the end of the task sequence we also get 'deployEndTime', and from those two values we can get the total build time.

The problem is that SOME of our deployments are recording a 'deployStartTime' that is an hour ahead of the actual time, and so the 'deployStartTime' is AFTER the 'deployEndTime' (because once it reboots into Windows 7, the time is correct), which messes up our calculations.

Our assumption is that this must be due to Daylight Savings Time, but why does it only happen on some builds?

Does it have to do with when the boot media was generated? That seems unlikely, but since we have lots of techs out there deploying machines (we only use USB boot media, no PXE), the only difference we can think of is the age of their boot ISOs.

I've done some research, and apparently WinPE just ignores Daylight Savings Time? But why would most of our builds have the correct time in WinPE, but some of them do not?

EDIT: We are in California, so Pacific Time Zone.


↧

Unable to complete Sysprep & Capture TS / Windows 8.1 / MDT 2013 / ADK8.1

March 23, 2015, 1:09 pm
$
0
0

Good afternoon everyone. I am  having difficulty succesfully running a Sysprep and Capture of a reference virtual machine i've created. The environment details are below:

  • Reference VM is on Hyper-V (Server 2012R2, Gen2 EFI)
  • Reference VM is a Windows 8.1 Host
  • Reference VM is a customized 8.1 image, not the vanilla RTM
  • Booted into Audit mode. No user profiles outside of the built-in admin created.
  • ADK 8.1 Installed
  • MDT 2013 Installed
  • Already installed the LTIApply takeown mod (https://support.microsoft.com/en-us/kb/2797676?wa=wsignin1.

I keep getting the following errors: 

The BDD log is linked here. Please shoot me any suggestions if possible. I'm truly out of ideas. 


↧
↧

Applying User specific settings and files to all new user profiles

March 13, 2015, 10:31 am
$
0
0

We have a handful of user profile specific files (located in  %APPDATA% and %LOCALAPPDATA%) and registry settings (HKCU) we want to ensure are applied for any new user profile on machines setup with MDT. 

For example, we have a file "config.ini" that needs to be in "%appdata%\Some Directory" for any user who logs on to a machine.

Im familiar with the using the CopyProfile from Default Profile for accomplishing this for registry entries at least, but this requires us to create a new build image each time we need to update. Hoping there is something that can be handled as part of the Task Sequence.

Whats the best/easiest way to accomplish this?

Thanks!




↧

Error "No task sequences are available (TaskSequences.xml does not exist, is empty, or is inaccessible)"

March 24, 2015, 7:22 am
$
0
0

Guys,

Please I urgently need help with this issue. Since yesterday afternoon, we are getting the following error when imaging a machine: "No task sequences are available (TaskSequences.xml does not exist, is empty, or is inaccessible)."

When I check the deployment share control folder, TaskSequences.xml is listed and as far as I can tell, everything looks fine. I went ahead and deleted the most recent 2 task sequences created and updated the deployment share but still no luck. When I try to pull up the BDD.Log from a trial machine, cmd prompt is telling me there is no MININT folder listed.

Unfortunately I don't have a backup copy of my deployment share control folder.

↧

MDT 2013 Roles and features failing to install for server 2012 r2

August 25, 2014, 7:52 am
$
0
0

I am having issues trying to apply Server 2012r2 Roles and features via MDT 2013.

Below I have attached the log.

<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[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.]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Roles will be installed.]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Roles specified in Role:]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  FileAndStorage-Services]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[RoleServices specified in RoleService:]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  File-Services]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  Storage-Services]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Features specified in Feature:]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  NET-Framework-Features]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  NET-Framework-Core]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  NET-WCF-TCP-PortSharing45]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  InkAndHandwritingServices]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  Server-Media-Foundation]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  RDC]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  SNMP-Service]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  SNMP-WMI-Provider]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  Telnet-Client]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  User-Interfaces-Infra]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  Server-Gui-Mgmt-Infra]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  Desktop-Experience]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  Server-Gui-Shell]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  PowerShellRoot]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  PowerShell]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  PowerShell-V2]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoles.]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoleServices.]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSFeatures.]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property Parameters is now = -FeatureName FileAndStorage-Services]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Validating connection to \\WIN-7VSNJRF3PNO\DeploymentShare$\Operating Systems\Windows Server 2012 R2 SERVERSTANDARDCORE x64]LOG]!><time="10:45:23.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Mapping server share: \\WIN-7VSNJRF3PNO\DeploymentShare$]LOG]!><time="10:45:24.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Already connected to server WIN-7VSNJRF3PNO as that is where this script is running from.]LOG]!><time="10:45:24.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Copying source files locally from \\WIN-7VSNJRF3PNO\DeploymentShare$\Operating Systems\Windows Server 2012 R2 SERVERSTANDARDCORE x64\sources\sxs]LOG]!><time="10:45:24.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTI ERROR - Unhandled error returned by ZTIOSRole: Path not found (76)]LOG]!><time="10:45:27.000+000" date="08-25-2014" component="ZTIOSRole" context="" type="3" thread="" file="ZTIOSRole">


↧
Search

Deploying Apps with Roles not working very well.

April 27, 2010, 10:46 am
$
0
0

I have deployed an app using a role associated to a specific computer.

I have other apps that I have installed with the deployment if they are listed on the 'Applications' tab using the 'Location', but If I put them in a role and then add the role to the 'Roles' tab for the location they do not get installed.

Anyone have any ideas why an app install works for a 'computer' but not for a 'location'?

↧
↧

Possible to resume deployment?

February 20, 2015, 12:31 pm
$
0
0

On occasion we have a troublesome application that hangs during installation forcing us to manually reboot or an application that automatically reboots the machine during deployment. After this reboot, it goes directly to the desktop and does not resume. MDT monitoring also shows its still in the "Application Installation" phase. Is it possible to "resume" the MDT deployment where it left off?

Thanks!


↧

MDT 2012 UNC Deployment Failure with static IP.

March 10, 2015, 11:33 am
$
0
0

I am having trouble getting my UNC deployment to run the State Restore phase. I am operating on a network without DHCP and have successfully connected to the network share and ran the Task Sequence. After the reboot, however, the static ip doesn't get set and the deployment can't continue.

Upon inspection of the BDD.log I ran across the entry in the State Restore section that pertains to setting the static ip.

WMI Function: Adapter.EnableStatic(IPAddress,SubnetMask) FAILURE: -2147217405 Unknown Error: -2147217405

If I log in and run the LiteTouch.wsf file as an administrator, the task sequence starts running again and the static ip gets applied.

Why is this not happening automatically?


↧

Error creating catalog file

March 5, 2015, 11:38 pm
$
0
0

On the MDT2013 deployment everything is working fine. But after a change lets say a new image to import and after the import make a task sequence. Then thru properties try to edit the unattend there it goes wrong several times now.

When choose edit unattend a error appears after a while:

Non-zero return code from catalog utility, rc = 2002

Cannot create catalog.

I must edit the unattend.xml because there must be the option copyprofile=true in the TS.

The question is where does it goes wrong?
Delete the excisting (Image) operating system in MDT2013 (name.wim)
Import a (Image) operating system in MDT2013
Delete the excisting TS
Create a new TS to deploy the imported image
Try to edit unattend.

If i go to the original image folder there is no .clg file. So have read on the internet to copy the original .clg from the Windows 7 SP1 DVD to the image folder which i want to deploy and naming it the same as the image.wim file but with the extension.clg

After this i open the system image editor and try to open the .clg file but this also reproduce the error... So deleting the clg and open system image editor and let it create a new catalog works, but every time i import a new task sequence and do above again i must create that catalog file again.

I have made a new deploymentshare and copied all to that new deployment share. However when doiing above again the error by edite unattend.xml creating the catalog is the same.

What can be the cause of this?

freddie

↧

Windows 8.1 file association

February 26, 2015, 3:35 am
$
0
0

Hi, all!

I'm trying associate .tiff file against MODI 2007.

So, I've prepared reference .xml with associations with Dism /online

After that I've imported that xml to PC with Dism /online, dism says that operation completed correctly

Dism /online /get-defaultappassociation shows me that .tiff associated against MODI

But, nothing happens, tiff opens with photo vierwer

If I export xml from that PC it shows that .tiff associated against photo vierwer

What;s the problem? Does anybody know?

↧
↧

Wizard Pane Based on Task Sequence selection

March 25, 2015, 1:26 pm
$
0
0

Hi

I have create a custom MDT wizard pane which has drop down to select the type of server like "IIS" or "SQL" or "Base OS" to install during deployment of Windows 2008 task sequence. User would be able to chose it from the drop down and it works fine.

Have created new task sequence to deploy 2012 and we have only 2 types of server "IIS" or "Base OS" the user should be able to chose from only these. Have created another MDT wizard pane for 2012.

Here is the problem.

Could some one let me know how to create a condition so that when user select 2008 Task sequence they get the first custom page and if they chose 2012 they get the other custom page. Now even if I run 2012 task sequence they get the first custom wizard pane.


↧

FAILURE ( 5640 ): FALSE: Verify File: \\SERVER\DeploymentShare\Operating Systems\Image 11-13-2014.wim\image.wim ERROR

March 25, 2015, 2:24 pm
$
0
0

Guys,

I need help with this error please. I have a WDS in building 13 and another 1 in building 31; Both servers have MDT 2013. At some point, both deployment shares were linked via MDT but I deleted that few days to solve some deployment share corruption in building 31 WDS.

Presently I have 2 32bit images (my 64bit images work fine) giving me the following MDT error in BUILDING 13 during the image deployment:

FAILURE ( 5640 ): FALSE: Verify File: \\BUILDING 31 SERVER\DeploymentShare\Operating Systems\Image 11-13-2014.wim\image.wim

Litetouch deployment failed, Return Code = -2147467259 0x80004005

Failed to run the action: Install Operating System.

Unknown error (Error:00001608; Source: Unknown)

The Execution of the group (Install) has failed and the execution has been aborted. An action failed....

Please note, BUILDING 13 deployment share is not linked to BUILDING 31 deployment share. I don't understand why this error is pointing to BUILDING 31 deployment share.\\BUILDING 31 SERVER\DeploymentShare\Operating Systems\Image 11-13-2014.wim\image.wim  has been removed. I need the task sequence to point to\\BUILDING 13 SERVER\DeploymentShare\Operating Systems\Image 11-13-2014.wim. BUILDING 13 deployment Share task sequences are pointing to\\BUILDING 13 SERVER\DeploymentShare as well as my CustomSettings.ini and Bootstrap.ini 

1. I have diskpart and cleaned the disc, no luck.

2. I have checked the Install action for both images task sequences and even verified each action on both tasks and cant find any error.

3. I have re-generated the boot images and retyped \\BUILDING 13 SERVER\DeploymentShare on its CustomSettings.ini and Bootstrap.ini 

4. I am in the process of copying Image 11-13-2014.wim back to \\BUILDING 31 SERVER\DeploymentShare\Operating Systems BUT again I don't understand why these task sequences are pointing to building 31. If this step doesn't work, I will restore both images from a backup and re-added them to building 13 MDT. But I don't think these steps are the solution.I am out of ideas here...

↧
Search

Language Packs X86 Windows 8.1 update

March 26, 2015, 2:15 am
$
0
0

Hello,

in the past, i could shoud before installing an OS with language is installed.

At the moment this isn`t working for me anymore for X86-images --> x64 images are working ok.

The langue-packs i have installed in MDT are the following :

Maybe i need the 9600-image of the language pack? But i can not find that one on the microsoft download-page.

Anybody with a solution for this?

Thx

↧

Is there a way to do inline comments in customsettings.ini?

January 8, 2014, 11:16 am
$
0
0

For example this works:

; Install Microsoft Office
Applications001={4a26b8f5-69f1-4ccc-b86e-80ac637e3e5e}

But I'd rather do it like this (however this does not work):

Applications001={4a26b8f5-69f1-4ccc-b86e-80ac637e3e5e} ; Install Microsoft Office

Is there another comment character or some other way to use the semi-colon that wil allow me to do inline comments in CustomSettings.ini?

↧
↧

Run a powershell script with domain credentials during task sequence

March 26, 2015, 6:41 am
$
0
0

I have a powershell script that adds the computer it is run on to a security group.  If I log onto the computer with a domain account it works perfectly.  However, if it is run while logged on as the local admin account it fails with an error message that says the domain either doesn't exist or cannot be reached.

This is a problem because when a computer is being imaged the process runs with the local admin account.  Is there a way to run this script with domain credentials in the task sequence?

Thanks,

Andy

↧

(Err): 70: CreateObject(Microsoft.BDD.Utility) - Permission denied]

March 26, 2015, 4:25 pm
$
0
0

HI All,

  I have a Application to install but MDT failed with above error.

Also left the MININT and _TAskSequence folder in D Drive ( I have format OS and Data)

As

↧

LiteTouch install prematurely terminated

September 12, 2010, 7:17 pm
$
0
0

Good day,

I am building a LiteTouch task sequence for a Windows 7 Enterprise x64 deployment for a HP Probook 6550b laptop.

The task sequence has been initially tested for deployment on a Hyper-V virtual machine. The task sequence was successfully completed with four errors displayed in the usual wizard dialog box at the completion of deployment, related to specific application install tasks.

The task sequence was then tested for deployment on the reference hardware platform. The task sequence appears to have prematurely abnormally terminated. No completion wizard is displayed and the application install tasks were not completed.

So far I have made 5 attempts to deploy the installation onto the reference platform using x64, I am now trialling an older Pro x86 deployment for another model laptop to see if that is more successful. I have the MININT and _SMSTaskSequence folders copied from each of those deployment attempts. (Normally the _SMSTaskSequence folder is removed at the successful completion of a deployment sequence which is another indication of abnormal termination)

The question now is how to determine what is going wrong from the logs.

Using both MDT2010 original release and MDT2010 Update 1, both on Windows 7 Pro x86.

The Windows PE x64 LiteTouch image and the deployment task sequence are both injecting the network card driver for this platform. There are no problems being reported that appear to relate to network connectivity.

Thanks in advance

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