I'm working on Windows 7 OS Deployment and I need to build a check in my OSD TS to detect if the primary network is Wireless. If it's not on hard wire network I want to abort my OSD TS before it starts.

I've already thought about using the default gateway check to determine if it's on wireless. This method won't be practical as there's many wireless gateways across the huge enterprise and they can change without notice.

What method do you guys use in your OSD TS to detect if it's on wireless and how to do you handle this issue ?

Thanks very much for your helpful response.

Hi guys, in the midst of a project to refresh client Operating Systems - the refresh involves using the User State Migration Tool version 5 to capture user settings/preferences and data from old devices and restore to new machines once the Operating System and applications such as Office are deployed.

SCCM infrastructure is 2012 SP1. Source/old machines are running Windows Vista or Windows 7, Office 2007 and have the Enterprise Vault Add-In for Outlook version 9.0.2.1136. Target/new machines have Windows 7 SP1, Office 2013 and Enterprise Vault Add-In for Outlook version 10.0.3.1090. All operating systems are 32-bit.

USMT 5 has been extended with the hotfix for Office 2013 (new MigApp.xml) - otherwise the capture is effectively vanilla.

On machines where the User State Migration Tool is used every time Outlook is opened the following error is presented:

Either there is no default mail client or the current mail client cannot fulfill the messaging request.

If Outlook is started using outlook.exe /safe it opens without issue. If I disable the Enterprise Vault Add-In within Outlook, it opens without issue.

I’ve been through the following to no avail:

• http://support.microsoft.com/kb/813745
• http://www.symantec.com/business/support/index?page=content&id=TECH20486&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1377114331330xz9e5SBBuT28VInhuBHCHNIlGKF39rjY1sr1c
• Removing the Enterprise Vault Add-In and re-installing doesn’t resolve the issue, neither does the ResetEVClient.exe utility.
• Run fixmapi.exe to no avail.

A repair of Office itself fixes the problem, however this is not feasible across the thousands of machines we're looking to migrate!

What we have noted is that the issue affects every Windows profile on the machine, those copied over by the User State Migration Tool, but also new ones - so whatever is occurring is breaking Outlook/the Enterprise Vault Add-In for the machine, not a specific profile.

Finally, if we don't use USMT (not viable on the number of machines we have to replace!) I'm able to logon, and under a fresh user profile can open Outlook without issue.

If anyone has any ideas please let me know!

MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

I am working on a way to log the entire OS deployment.  I've setup my SMSTS.INI file like so and injected it into my boot media:

[Logging]
LOGLEVEL=0
LOGMAXSIZE=5242880
LOGMAXHISTORY=5

I'm also installing my ConfigMan agent with the following parameters:

LOGLEVEL=0 LOGMAXSIZE=5242880 LOGMAXHISTORY=5 /mp:<server>

However, I still only see two smsts log files (one with a timestamp and one without), and the earliest entries start at the OSDSETUPHOOK.EXE portion (BTW, is that when the machine reboots for the first time after the WinPE portion? It seems like it).

How can I get logging from the very beginning of the boot until the very end of the TS?

Hello. I am using a standard client MDT 2012 Task Sequence, deployed to Unknown Computers collection in SCCM 2012 SP1, using the UDI wizard to do the following: Set the volume for install, Join a domain, Install Packages. The first two sets work fine, however, the packages i define in the UDI do not install. When the deployment is complete, the status of all my package installs is "Install Status Unknown". The UDI sees the packges in SCCM no problem (the box is checked to run from task sequence on my packages). I don't have any applications created  yet, so I don't know if the problem persists with applications too. As far as I can tell, I have done nothing to alter the defaults in terms of setting variables.

I have not found a similar problem on these forums so far, so any help/guidance is most appreciated.

Thanks, Rich

My environment is SCCM 2012 SP1 with MDT 2012 update 1 integrated. I have used state migration points before in SCCM 2007 but am having some issues in my SCCM 2012 environment. My understanding is SCCM will automatically use an SMP if it is setup and the machine building built fails within its scope. However, when I run my default MDT Task Sequence (WinXP to Win7 migration on the same hardware) it fails each time. When I examine the logs I see errors about not finding the drive and it is using hardlinks. I do not have anything configured in my custom settings ini. Do I need to set variables to force it to use the SMP? If so, which ones are needed?

Thank you for the assistance.

Scanstate.log

OpenDevice failed with Exception: Win32Exception: Hardlink main store must support hardlinks: The system cannot find the drive specified. [0x0000000F]

ztiuserstate.log

Setting ConfigMgr variables to perform a hardlink migration.   
Property OSDMigrateAdditionalCaptureOptions is now = /hardlink /nocompress  
Property OSDMigrateAdditionalRestoreOptions is now = /hardlink /nocompress    ztiuserstate   
Property USMTLocal is now = True  
Property OSDStateStorePath is now = C:\StateStore   

I'm seeing some issues when using an OU (and child OUs) as a requirement for application deployment during OSD.

The target machine logs the application as "not required" during the Task Sequence, I'm guessing because SCCM hasn't got the OU information for the machine, yet. Is there any way I can trigger population of this data in ConfigMgr during OSD to facilitate this requirement specification.

I have a 'workaround' where I read the OU from ADDS however this won't work for IBCM clients - so I end up either having a working TS and breaking IBCM deployment of the applications, or vice versa.

Thanks,

Chris

MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

I am using MDT to populate some dynamic Task Sequence Variables, After the gather stage I take my MDT properties and use them to set TS Variables which are used to help simplify tasks at a later stage in the TS. The variables all seem to working during the Windows PE part of my OSD TS, however this does not appear to be the case in the full client OS.

For example I install Windows Language Packs dynamically based upon the TSVariable "%TargetComputerLanguage%" - this is simply a Run Command Line task;

DISM.exe /image:%OSDTargetSystemDrive%\ /ScratchDir:%OSDTargetSystemDrive%\windows\TEMP /Add-Package /PackagePath:%TargetComputerLanguage%\lp.cab

This task works without issue.

Later on, following reboots etc I try to use the same variable again in another Run Command Line task which should install the required IE10 language pack to match the Windows LP installed earlier;

C:\Windows\System32\wusa.exe X86\IE10-Windows6.1-LanguagePack-x86-%TargetComputerLanguage%.msu /quiet /norestart

This task fails every time. I know the TS variable exists as this task has a condition which will not action unless the variable exists.

Looking at the smsts log I can see that the command executed is not being populated with the value of %TargetComputerLanguage% - just the string that represents the variable itself i.e. "%TargetComputerLanguage%". Of course this fails.

I understand that the variables are not directly accessible following reboot into the full Operating System Environment, but I am calling this variable from the TS, so I understood this to be OK. Any ideas as to why this is failing - am I trying to do something here that will never work.

Thanks for taking a look and any thoughts/advice.

Chris

MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

Strange one this... on non-SSD laptops this application as part of a Windows 7 OSD works just fine, on SSD-equipped machines it fails, every time. All clients are Dell E6330 laptops.

SMSTS.log - noting failure of installed application as cause of T/S failure.

The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)	TSManager	18/07/2013 14:16:59	2768 (0x0AD0)
Failed to run the last action: Install Laptop "Tier 2" Applications; Stage 1/1. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows)	TSManager	18/07/2013 14:16:59	2768 (0x0AD0)

AppDiscovery.log:

+++ MSI application not discovered [MSI Product Code: {54109BEE-53BA-4284-8A50-41901453584D}, MSI Product version: ]	AppDiscovery	18/07/2013 14:15:43	3672 (0x0E58)+++ Did not detect app deployment type Open Mobile 2.4.0-19833 X86 EN - MSI(ScopeId_43347163-BC72-4CCA-A9E9-DBCC13F55603/DeploymentType_ac51451a-4422-4310-b754-dd4879c7c2cf, revision 3) for system.	AppDiscovery	18/07/2013 14:15:43	3672 (0x0E58)
   ActionType - Install will use Content Id: Content_0e0ffc58-7b4e-4dac-8499-fc725c9a5ee8 + Content Version: 1 for AppDT "Open Mobile 2.4.0-19833 X86 EN - MSI" [ScopeId_43347163-BC72-4CCA-A9E9-DBCC13F55603/DeploymentType_ac51451a-4422-4310-b754-dd4879c7c2cf], Revision - 3	AppDiscovery	18/07/2013 14:15:43	3672 (0x0E58)
   ActionType - Install will use Content Id: Content_0e0ffc58-7b4e-4dac-8499-fc725c9a5ee8 + Content Version: 1 for AppDT "Open Mobile 2.4.0-19833 X86 EN - MSI" [ScopeId_43347163-BC72-4CCA-A9E9-DBCC13F55603/DeploymentType_ac51451a-4422-4310-b754-dd4879c7c2cf], Revision - 3	AppDiscovery	18/07/2013 14:15:44	3672 (0x0E58)

AppEnforce.log

+++ Starting Install enforcement for App DT "Open Mobile 2.4.0-19833 X86 EN - MSI" ApplicationDeliveryType - ScopeId_43347163-BC72-4CCA-A9E9-DBCC13F55603/DeploymentType_ac51451a-4422-4310-b754-dd4879c7c2cf, Revision - 3, ContentPath - C:\WINDOWS\ccmcache\1k, Execution Context - System	AppEnforce	18/07/2013 14:16:49	3672 (0x0E58)
    A user is not logged on to the system.	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)
    Performing detection of app deployment type Open Mobile 2.4.0-19833 X86 EN - MSI(ScopeId_43347163-BC72-4CCA-A9E9-DBCC13F55603/DeploymentType_ac51451a-4422-4310-b754-dd4879c7c2cf, revision 3) for system.	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)+++ MSI application not discovered [MSI Product Code: {54109BEE-53BA-4284-8A50-41901453584D}, MSI Product version: ]	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)
    App enforcement environment: 
	Context: Machine
	Command line: msiexec /i "Open Mobile-V2.4.0-19833-V0.007.msi" TRANSFORMS=OpenMobile_v240.mst REBOOT=REALLYSUPPRESS /q
	Allow user interaction: No
	UI mode: 0
	User token: null
	Session Id: 4294967295
	Content path: C:\WINDOWS\ccmcache\1k
	Working directory: 	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)
    Prepared working directory: C:\WINDOWS\ccmcache\1k	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)
Found executable file msiexec with complete path C:\WINDOWS\system32\msiexec.exe	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)
    Prepared command line: "C:\WINDOWS\system32\msiexec.exe" /i "Open Mobile-V2.4.0-19833-V0.007.msi" TRANSFORMS=OpenMobile_v240.mst REBOOT=REALLYSUPPRESS /q /qn	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)
Valid MSI Package path = C:\WINDOWS\ccmcache\1k\Open Mobile-V2.4.0-19833-V0.007.msi	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)
    Advertising MSI package [C:\WINDOWS\ccmcache\1k\Open Mobile-V2.4.0-19833-V0.007.msi] to the system.	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)
    Executing Command line: "C:\WINDOWS\system32\msiexec.exe" /i "Open Mobile-V2.4.0-19833-V0.007.msi" TRANSFORMS=OpenMobile_v240.mst REBOOT=REALLYSUPPRESS /q /qn with system context	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)
    Working directory C:\WINDOWS\ccmcache\1k	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)
    Post install behavior is BasedOnExitCode	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)
    Waiting for process 4024 to finish.  Timeout = 120 minutes.	AppEnforce	18/07/2013 14:16:51	3672 (0x0E58)

That's the end of the AppEnforce.log, even after logging on to the client post T/S failure - what I'm concerned about it where on earth is the rest of the deployment information, a normal deployment during the T/S looks like this:

AppEnforce.log - note the detection of the process exit, exit code etc.

+++ Starting Install enforcement for App DT "Riverbed Steelhead Mobile 3.1.3d X86 - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_43347163-BC72-4CCA-A9E9-DBCC13F55603/DeploymentType_9a3c2855-0622-468a-a04a-3d145128c657, Revision - 5, ContentPath - C:\WINDOWS\ccmcache\1j, Execution Context - System	AppEnforce	18/07/2013 14:14:00	3360 (0x0D20)
    A user is not logged on to the system.	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
    Performing detection of app deployment type Riverbed Steelhead Mobile 3.1.3d X86 - Windows Installer (*.msi file)(ScopeId_43347163-BC72-4CCA-A9E9-DBCC13F55603/DeploymentType_9a3c2855-0622-468a-a04a-3d145128c657, revision 5) for system.	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)+++ Application not discovered. [AppDT Id: ScopeId_43347163-BC72-4CCA-A9E9-DBCC13F55603/DeploymentType_9a3c2855-0622-468a-a04a-3d145128c657, Revision: 5]	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
    App enforcement environment: 
	Context: Machine
	Command line: msiexec /i "SteelheadMobilex32.msi" REBOOT=ReallySuppress /q
	Allow user interaction: No
	UI mode: 0
	User token: null
	Session Id: 4294967295
	Content path: C:\WINDOWS\ccmcache\1j
	Working directory: 	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
    Prepared working directory: C:\WINDOWS\ccmcache\1j	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
Found executable file msiexec with complete path C:\WINDOWS\system32\msiexec.exe	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
    Prepared command line: "C:\WINDOWS\system32\msiexec.exe" /i "SteelheadMobilex32.msi" REBOOT=ReallySuppress /q /qn	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
Valid MSI Package path = C:\WINDOWS\ccmcache\1j\SteelheadMobilex32.msi	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
    Advertising MSI package [C:\WINDOWS\ccmcache\1j\SteelheadMobilex32.msi] to the system.	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
    Executing Command line: "C:\WINDOWS\system32\msiexec.exe" /i "SteelheadMobilex32.msi" REBOOT=ReallySuppress /q /qn with system context	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
    Working directory C:\WINDOWS\ccmcache\1j	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
    Post install behavior is ForceReboot	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
    Waiting for process 2832 to finish.  Timeout = 120 minutes.	AppEnforce	18/07/2013 14:14:01	3360 (0x0D20)
    Process 2832 terminated with exitcode: 0	AppEnforce	18/07/2013 14:14:04	3360 (0x0D20)
    Looking for exit code 0 in exit codes table...	AppEnforce	18/07/2013 14:14:04	3360 (0x0D20)
    ConfigMgr will request a hard reboot after successful enforcement	AppEnforce	18/07/2013 14:14:04	3360 (0x0D20)++++++ App enforcement completed (3 seconds) for App DT "Riverbed Steelhead Mobile 3.1.3d X86 - Windows Installer (*.msi file)" [ScopeId_43347163-BC72-4CCA-A9E9-DBCC13F55603/DeploymentType_9a3c2855-0622-468a-a04a-3d145128c657], Revision: 5, User SID: ] ++++++	AppEnforce	18/07/2013 14:14:04	3360 (0x0D20)

This application runs prior to the failing application..

Tried wrapping it up in a batch file, same result.

The deployment type is working, and ironically the application is installed on the SSD-equipped clients.

Any ideas most welcome!

MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

During Windows 7 SP1 x86 image deployment (initial build/capture completed without issue) I have a problem where updates are failing to install, the TS gets stuck at "Downloading 5 of 5 Updates (100% complete)"

The smsts.log shows lots of "Waiting for job status notification" messages - eventually the whole thing times out and fails:

Refreshing Updates	InstallSWUpdate	15/05/2013 20:58:24	2616 (0x0A38)
Successfully initiated RefreshUpdates operation 	InstallSWUpdate	15/05/2013 20:58:25	2616 (0x0A38)
Waiting for RefreshUpdates complete notification from Updates Deployment Agent	InstallSWUpdate	15/05/2013 20:58:25	2616 (0x0A38)
Notification received, RefreshUpdates have been completed	InstallSWUpdates	15/05/2013 21:01:33	3032 (0x0BD8)
Received RefreshUpdates complete notification from Updates Deployment Agent	InstallSWUpdate	15/05/2013 21:01:33	2616 (0x0A38)
RefreshUpdates operation has been completed, hr=0x00000000	InstallSWUpdate	15/05/2013 21:01:33	2616 (0x0A38)
Signaled RefreshComplete notification	InstallSWUpdates	15/05/2013 21:01:33	3032 (0x0BD8)
GetIPriviledgedInstallInterface successful	InstallSWUpdate	15/05/2013 21:01:33	2616 (0x0A38)
Installing all updates targetted for this computer	InstallSWUpdate	15/05/2013 21:01:33	2616 (0x0A38)
Checking if the active request handle: {A173CB00-7C38-4328-A2B3-C1C0A7686A9B} is valid.	InstallSWUpdate	15/05/2013 21:01:33	2616 (0x0A38)
CoCreateInstance succeeded	InstallSWUpdate	15/05/2013 21:01:33	2616 (0x0A38)
Active request handle: {A173CB00-7C38-4328-A2B3-C1C0A7686A9B} is valid.	InstallSWUpdate	15/05/2013 21:01:33	2616 (0x0A38)
Installation of updates started	InstallSWUpdate	15/05/2013 21:01:33	2616 (0x0A38)
Waiting for installation job to complete	InstallSWUpdate	15/05/2013 21:01:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:02:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:03:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:04:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:05:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:06:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:07:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:08:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:09:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:10:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:11:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:12:33	2616 (0x0A38)
Waiting for job status notification ...	InstallSWUpdate	15/05/2013 21:13:33	2616 (0x0A38)

As I said, during the master image build/capture install updates works just fine, however this TS fail every time.

Nothing in CAS.log of any use, nor any of the Update*.log, WindowsUpdate.log or WUAHandler.log files.

I've check for updates that are deployed but not downloaded - all packages look O.K. I've also disabled 'clients can share content with other clients on the same subnet' on the update deployment to the OSD collection.

If anyone has any suggestions I'd be most grateful :)

Thanks, Chris

MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

I'm currently Having issues importing some of my prestaged content to my remote distribution point. I'm getting the following errors at the end of the PrestageContent.log. (edited to remove timestamps)

CContentDefinition::ExpandContentDefinitionItems failed; 0x80070003 PrestageContent 

Failed to expand content of package CGN0003C PrestageContent

ArchiveFile::Transform2ClassicContentForSMB failed; 0x80004005 PrestageContent 

Error transforming single instance storage to classic storage for SMB access PrestageContent 

ArchiveFile::RemoteDpPostExtractProcessing failed; 0x80004005 PrestageContent 

ArchiveFile::PostExtractProcessing failed; 0x80004005 PrestageContent

ArchiveFile::ExtractContent failed; 0x80004005 PrestageContent

I have been able to prestage some packages, mainly my OSD image file but the issue seems to be with the driver packages. at the beginning of the log file it statesContent type:"LegacyContentBased" for the non working packages while my working packages specify a "Classic" content type. I presume i<m looking at the right place with the issue, i just don't know what to do about it. Any Suggestions?

Hi

I work in an educational environment where instructors are always requesting changes. My question is for those of you that work in an environment that is constantly changing, how do you handle software additions, or configuration changes, after the fact  having laid down a solid image?

What do you do if a software addition request is just next to impossible to silently push, how do you avoid re-imaging scenario.

I have a Windows 8 task sequence that using the query "ISLaptop equals TRUE" should install VPN. During the task sequence, it runs through the VPN software install and completes without any errors, but when you log into the laptop the software is not installed.

Any ideas?

Currently doing a migration form SCCM 2007 to 2012 Sp1.  

I am trying to create the build and capture task sequences for deploying Server 2008 and Server 2012.  However I notice something very different between the 2012 build and capture task sequence and the 2007 one.

The 2007 one allowed you to choose the original 2008/2012 from your operating system install packages and then you chose the edition: standard, core, enterprise, data center, etc.  In SCCM 2007, I have two of those build and capture task sequences, one for 2008 Std and one for 2008 Ent.

However in the 2012 build and capture task sequence, I can only choose image packages, which are the .WIM files I captured in SCCM 2007 and copied over manually and created/distributed in SC 2012 already.  I can't select my operating system installers, and yes I do have them setup and distributed.  I no longer have the capability to choose the original 2008 install package and then select standard, ent, core, data center.

What am I missing or doing wrong here?  I am selecting New Task Sequence and then selecting Build and Capture a reference operating system image.  My only options when I click browse never to Image Package are existing customized WIMs.  

Hey Guys I've been getting to know USMT but there is one thing I'm still unclear about.

During an OSD do you need to have the Users Profile captured beforehand?

I was under the assumption when you use SMP and have computer association you can do the capture / restore steps in the same task sequence, but so far it has not worked that way. is there something i'm missing?

or do you need to have users profile captured beforehand with a separate task sequence?

Hi Guys,

I have a huge problem. Heres the dp

SCCM 2012 running on Windows Server 2008r2 on ESX with a VMXnet3 10gb Uplink

Autocast

1gb to the client

Im getting 20-30 % client nic usage on a single client autocast when i put 10 on the autocast client nic useage drops to 0.5-2%

On the Server we are seeing next to nothing i think it is 1,500,000bps under resourse monitor

We have all Cisco Gear, We have tried all sorts of settings currently set at

ApBlockSize=1385

TpCacheSize=7550 we have also tried 3145 and it makes no diffence to the speed.

And it takes ages to deploy a 36gb wim file and usual about 40% of the time we get Sparse file encouted when decompressing the wim after file transfur then a hash check failed in the SMSTSlog file

Cisco Guys have looked no issues from their end....

is it the VMXnet / 2008r2 / WDS setting anyone else got these horrible teething issues its so close the the end of the year if i have to go to using ghost to deploy 4500 machines to prevent corruption.. ill go crazy..

Some people are saying this occours with a 2008r2 distrubution point is this true?

I have read all these none of them make any difference

http://support.microsoft.com/kb/2582106?wa=wsignin1.0

Hi everyone,

I am having a request to be able to use OSD on really slow network devices.

They would like to be able to create a standalone media, send that media to a computer on a hidden drive (F drive), and then launch the task sequence.

The media will contain every drivers and software.

Is there a way to achieve this or is there a way to do something similar using SCCM 2012 SP1?

Thanks

Mat

After I make a change to the UDI (add another OU to select), when I run the Task Sequence it doesn't show me the new OU added.

The steps that I take after I make a change to the UDI are:

1. 'Update Distribution Points' of the package that contains the UDI

2. Deploy the task sequence to the 'All Unknown Computers' collection

3. Run the Task Sequence via the media boot iso.

I'm sure there a small think I'm missing, but I can't figure what exactly what - I'm new to the task sequence process.

I have the latest patch installed - Version 5.0.7804.1300.

Hi

I created a task seqeunce which is working very well without any errors. When I use this working task sequence to create a prestaged media task sequence applications not installed at all. I recreated the image etc. but I still get the same errors in my log. I get these error for each application, not only the one mentioned.

Any ideas

spCIStore->StoreCIFromDisk(pInfo), HRESULT=80004005 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,2237)    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
StoreCIFromDisk: Unable to store CI: 0x80004005    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
spAppSDK->StoreCIFromDisk (&PathInfo), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,912)    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
StoreCIFromDisk failed    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
StoreAppDocuments failed; 0x80004005    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
TS::Utility::StoreAppDocuments (sAppDocs.c_str()), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,880)    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
StoreAppDocuments failed    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
Step 2 out of 2 complete    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
Install application action failed: '001 Microsoft Visual C++ 2005 Redistributable (x86)'. Error Code 0x80004005    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
Sending error status message    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
sClientGUID.empty()==false, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,5699)    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
The client GUID must be set in an environment variable    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
Non fatal error 0x80004005 in sending task sequence execution status message to MP    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
Install application action cannot continue. ContinueOnErrorFlag is set to false.    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
hrInstallation, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,808)    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
pInstall->InstallApplications(saAppNames, sContinueOnError), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\main.cpp,277)    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
Install Static Applications failed, hr=0x80004005    InstallApplication    22.05.2013 20:13:25    2544 (0x09F0)
Process completed with exit code 2147500037    TSManager    22.05.2013 20:13:25    1528 (0x05F8)
!--------------------------------------------------------------------------------------------!    TSManager    22.05.2013 20:13:25    1528 (0x05F8)
Failed to run the action: Microsoft Visual C++ 2005 x86 installieren.
Unknown error (Error: 80004005; Source: Unknown)    TSManager    22.05.2013 20:13:25    1528 (0x05F8)
Do not send status message in full media case    TSManager    22.05.2013 20:13:25    1528 (0x05F8)
Set a global environment variable _SMSTSLastActionRetCode=-2147467259    TSManager    22.05.2013 20:13:25    1528 (0x05F8)
Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager    22.05.2013 20:13:25    1528 (0x05F8)
Clear local default environment    TSManager    22.05.2013 20:13:25    1528 (0x05F8)
The execution engine ignored the failure of the action (Microsoft Visual C++ 2005 x86 installieren) and continues execution    TSManager    22.05.2013 20:13:25    1528 (0x05F8)
Do not send status message in full media case    TSManager    22.05.2013 20:13:25    1528 (0x05F8)
Updated security on object C:\_SMSTaskSequence.    TSManager    22.05.2013 20:13:25    1528 (0x05F8)
Set a global environment variable _SMSTSNextInstructionPointer=121    TSManager    22.05.2013 20:13:25    1528 (0x05F8)

Thanks

Joachim

I have a task sequence that fails while downloading the WIM. It starts downloading, gets to a certain percentage then starts over, it does this a couple times before failing with error 80070002.

ReadDataAndWriteToFile() failed with 0x80072ee2 when downloading 16% of file C:\_SMSTaskSequence\Packages\PRK00025\ENx64W7.wim

ReadDataAndWriteToFile() failed with 0x80072ee2 when downloading 39% of file C:\_SMSTaskSequence\Packages\PRK00025\ENx64W7.wim

Here's the really strange part, If I F8 and ping the server, it replies and the download continues. The ping is losing packets which I suspect is why the download is failing. I plug into the same port with a working laptop and I don't lose packets. I tried updating the drivers in the Boot WIM to the most current version, older versions, same result. I know it's not Network Access Account since the download starts (and finishes as long as I'm pinging). Any ideas?

Thanks!