Share via

Failed to run the last action: Upgrade Operating System. Execution of task sequence failed. Unspecified error (Error: 80004005; Source: Windows)

  • Article

Question

Thursday, April 4, 2019 4:15 PM

Environment

  • Main Site Server 2012 R2
  • 2 Distribution points both 2012 R2
  • 4400 clients
  • Configuration Manager 1806

I am testing the Windows 10 1809 Pro task sequence upgrade, I have deployed it to a test machine through the software center and to another machine without any issue. I had tested with another set of about 5 computers and only 1 out of 5 were successful, here is the SMSTS.log any help would be appreciated. I have also made exceptions on Mcafee for folder exceptions for the following locations 

  • C:\windows\CCM
  • C:\windows\CCMCACHE
  • C:\windows\ccmsetup
  • Details for image : C:\SMSTaskSequence\Packages\P01000B3\sources\install.wim
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Index : 5
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Name : Windows 10 Pro
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Description : Windows 10 Pro
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Size : 14,604,374,236 bytes
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    WIM Bootable : No
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Architecture : x64
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Hal : <undefined>
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Version : 10.0.17763
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    ServicePack Build : 107
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    ServicePack Level : 0
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Edition : Professional
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Installation : Client
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    ProductType : WinNT
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    ProductSuite : Terminal Server
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    System Root : WINDOWS
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Directories : 19468
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Files : 90613
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Created : 10/29/2018 - 5:52:43 PM
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Modified : 10/29/2018 - 6:19:25 PM
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Languages :
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    en-US (Default)
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    The operation completed successfully.
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    The operation completed successfully.
    OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Validating  package for OS upgrade architecture OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Architecture of OS upgrade package is x64 OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Architecture of current OS is x64 OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Architecture of current OS matches architecture of new OS upgrade package. Can continue OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Validating  package for OS upgrade version OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    The version of source OS upgrade package '10.0.17763' is supported to be used in OS upgrade. We can continue OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    No timeout set for Windows Upgrade Setup OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Command line of Windows Setup upgrade: '"C:\SMSTaskSequence\Packages\P01000B3\SETUP.EXE" /ImageIndex 5 /auto Upgrade /quiet /noreboot /postoobe "C:\WINDOWS\SMSTSPostUpgrade\SetupComplete.cmd" /postrollback "C:\WINDOWS\SMSTSPostUpgrade\SetupRollback.cmd" /DynamicUpdate Disable' OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Command line for extension .EXE is "%1" %* OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Set command line: "C:\SMSTaskSequence\Packages\P01000B3\SETUP.EXE" /ImageIndex 5 /auto Upgrade /quiet /noreboot /postoobe "C:\WINDOWS\SMSTSPostUpgrade\SetupComplete.cmd" /postrollback "C:\WINDOWS\SMSTSPostUpgrade\SetupRollback.cmd" /DynamicUpdate Disable OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Executing command line: "C:\SMSTaskSequence\Packages\P01000B3\SETUP.EXE" /ImageIndex 5 /auto Upgrade /quiet /noreboot /postoobe "C:\WINDOWS\SMSTSPostUpgrade\SetupComplete.cmd" /postrollback "C:\WINDOWS\SMSTSPostUpgrade\SetupRollback.cmd" /DynamicUpdate Disable OSDUpgradeWindows 4/3/2019 5:25:32 PM 10900 (0x2A94)
    Process completed with exit code 3247440392 OSDUpgradeWindows 4/3/2019 5:28:44 PM 10900 (0x2A94)
    Windows Setup completed with exit code hexadecimal 0xC1900208 (decimal 3247440392) OSDUpgradeWindows 4/3/2019 5:28:44 PM 10900 (0x2A94)
    Saving exit code of Windows upgrade - hexadecimal 0xC1900208 (decimal 3247440392) -  to Task sequence environment variable '_SMSTSOSUpgradeActionReturnCode', as decimal string OSDUpgradeWindows 4/3/2019 5:28:44 PM 10900 (0x2A94)
    Windows Setup failed with hexadecimal exit code 0xC1900208 (decimal 3247440392). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online. OSDUpgradeWindows 4/3/2019 5:28:44 PM 10900 (0x2A94)
    Failing this task sequence step OSDUpgradeWindows 4/3/2019 5:28:44 PM 10900 (0x2A94)
    Enabling TSManager service OSDUpgradeWindows 4/3/2019 5:28:44 PM 10900 (0x2A94)
    smstsmgr service startup type is set to automatic OSDUpgradeWindows 4/3/2019 5:28:44 PM 10900 (0x2A94)
    Enabling CCMExec service OSDUpgradeWindows 4/3/2019 5:28:44 PM 10900 (0x2A94)
    CcmExec service startup type is set to automatic OSDUpgradeWindows 4/3/2019 5:28:44 PM 10900 (0x2A94)
    Setting the client out of provisioning mode OSDUpgradeWindows 4/3/2019 5:28:44 PM 10900 (0x2A94)
    Exiting SetClientProvisioningMode 0x00000000 OSDUpgradeWindows 4/3/2019 5:28:52 PM 10900 (0x2A94)
    upgrade.Run(), HRESULT=80004005 (upgradewindows.cpp,1454) OSDUpgradeWindows 4/3/2019 5:28:52 PM 10900 (0x2A94)
    Exiting with code 0x80004005 OSDUpgradeWindows 4/3/2019 5:28:52 PM 10900 (0x2A94)
    Process completed with exit code 2147500037 TSManager 4/3/2019 5:28:52 PM 9544 (0x2548)
    !! TSManager 4/3/2019 5:28:52 PM 9544 (0x2548)
    Failed to run the action: Upgrade Operating System. 
    Unspecified error (Error: 80004005; Source: Windows) TSManager 4/3/2019 5:28:52 PM 9544 (0x2548)
    Not in SSL TSManager 4/3/2019 5:28:52 PM 9544 (0x2548)
    Set a global environment variable _SMSTSLastActionRetCode=-2147467259 TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    Clear local default environment TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    Let the parent group (Upgrade the Operating System) decides whether to continue execution TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    Failed to run the last action: Upgrade Operating System. Execution of task sequence failed.
    Unspecified error (Error: 80004005; Source: Windows) TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    Not in SSL TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    **************************************************************************** TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    Task sequence execution failed with error code 80004005 TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    Cleaning Up. TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    Removing Authenticator TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    Cleaning up task sequence folder TSManager 4/3/2019 5:28:53 PM 9544 (0x2548)
    Unable to delete directory C:\SMSTaskSequence\Packages\P01000B3\sources (0x80070091).  Continuing. TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    Unable to delete directory C:\SMSTaskSequence\Packages\P01000B3 (0x80070091).  Continuing. TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    Unable to delete directory C:\SMSTaskSequence\Packages (0x80070091).  Continuing. TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    Unable to delete file C:\SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    Failed to delete directory 'C:\SMSTaskSequence' TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    SetNamedSecurityInfo() failed. TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    SetObjectOwner() failed. 0x80070005. TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    RemoveFile() failed for C:\SMSTaskSequence\Packages\P01000B3\sources\setupprep.exe. 0x80070005. TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    RemoveDirectoryW failed (0x80070091) for C:\SMSTaskSequence\Packages\P01000B3\sources TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    RemoveDirectoryW failed (0x80070091) for C:\SMSTaskSequence\Packages\P01000B3 TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    RemoveDirectoryW failed (0x80070091) for C:\SMSTaskSequence\Packages TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    SetNamedSecurityInfo() failed. TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    SetObjectOwner() failed. 0x80070005. TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    RemoveFile() failed for C:\SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    RemoveDirectoryW failed (0x80070091) for C:\SMSTaskSequence TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    Deleting volume ID file C:\SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    Successfully unregistered Task Sequencing Environment COM Interface. TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    Executing command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister TSManager 4/3/2019 5:28:55 PM 9544 (0x2548)
    ==========[ TsProgressUI started in process 840 ]========== TsProgressUI 4/3/2019 5:28:56 PM 648 (0x0288)
    Command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister TsProgressUI 4/3/2019 5:28:56 PM 648 (0x0288)
    Unregistering COM classes TsProgressUI 4/3/2019 5:28:56 PM 648 (0x0288)
    Unregistering class objects TsProgressUI 4/3/2019 5:28:56 PM 648 (0x0288)
    Shutdown complete. TsProgressUI 4/3/2019 5:28:56 PM 648 (0x0288)
    Process completed with exit code 0 TSManager 4/3/2019 5:28:56 PM 9544 (0x2548)
    Successfully unregistered TS Progress UI. TSManager 4/3/2019 5:28:56 PM 9544 (0x2548)
    Start to cleanup TS policy TSManager 4/3/2019 5:28:56 PM 9544 (0x2548)
    End Task Sequence policy cleanup TSManager 4/3/2019 5:28:58 PM 9544 (0x2548)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 4/3/2019 5:28:58 PM 9544 (0x2548)
    GetTsRegValue() is unsuccessful. 0x80070002. TSManager 4/3/2019 5:28:58 PM 9544 (0x2548)
    End program: TSManager 4/3/2019 5:28:58 PM 9544 (0x2548)
    Error executing Task Sequence Manager service. Code 0x80004005 TSManager 4/3/2019 5:28:58 PM 9544 (0x2548)
    Sending error status message TSManager 4/3/2019 5:28:58 PM 9544 (0x2548)
    Not in SSL TSManager 4/3/2019 5:28:58 PM 9544 (0x2548)
    Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs TSManager 4/3/2019 5:28:58 PM 9544 (0x2548)

Sean J Lehne

All replies (8)

Friday, April 5, 2019 2:27 PM ✅Answered | 1 vote

Looks like the Client Proxy is blocking the upgrade?

<?xml version="1.0" encoding="utf-8"?>
<CompatReport xmlns="http://www.microsoft.com/ApplicationExperience/UpgradeAdvisor/01012009" MigXmlFile="NWVkzcJlykS4wzDk.3.8.0.0_APPRAISER_Migration.xml"><System X64Capable="True" X64Running="True"/><Hardware><HardwareItem HardwareType="Setup_BitlockerNoTargetSupport"><CompatibilityInfo BlockingType="None"/></HardwareItem><HardwareItem HardwareType="Setup_TargetIsNonStagedBuild"><CompatibilityInfo BlockingType="None"/></HardwareItem><HardwareItem HardwareType="Setup_LanguagePackDetected"><CompatibilityInfo BlockingType="None"/></HardwareItem><HardwareItem HardwareType="Setup_LicenseActivation"><CompatibilityInfo BlockingType="None"/></HardwareItem><HardwareItem HardwareType="Setup_FeaturesOnDemandDetected"><CompatibilityInfo BlockingType="None"/></HardwareItem><HardwareItem HardwareType="Setup_PendingFirmwareUpdateWithPower"><CompatibilityInfo BlockingType="None"/></HardwareItem><HardwareItem HardwareType="Setup_FlightSigningEnabled"><CompatibilityInfo BlockingType="None"/></HardwareItem><HardwareItem HardwareType="Setup_SecureBoot"><CompatibilityInfo BlockingType="None"/></HardwareItem></Hardware><SystemInfo UplevelEdition="Windows 10" OSMajorVersion="10" OSMinorVersion="0"/>
<Devices/>
<DriverPackages>
<DriverPackage Inf="oem49.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem46.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem53.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem14.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem18.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem69.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem25.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem47.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem9.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem2.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem43.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem57.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem3.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem80.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem74.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem101.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem37.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem45.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem103.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem94.inf" BlockMigration="True" HasSignedBinaries="False"/>
<DriverPackage Inf="oem93.inf" BlockMigration="True" HasSignedBinaries="False"/>
<DriverPackage Inf="oem72.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem1.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem83.inf" BlockMigration="False" HasSignedBinaries="True"/>
<DriverPackage Inf="oem96.inf" BlockMigration="False" HasSignedBinaries="True"/>
</DriverPackages><Programs><Program Name="McAfee Client Proxy" Id="0000c8a3d9987deb24a7b938f396cbcb424500000904" IconId="0000c8a3d9987deb24a7b938f396cbcb424500000904"><CompatibilityInfo BlockingType="Hard" StatusDetail="UpgradeBlock"/><Action Name="AutoUninstall" Link="wsc:wica:_0000c8a3d9987deb24a7b938f396cbcb424500000904" DisplayStyle="Link" ResolveState="NotRun"/></Program><Program Name="McAfee Endpoint Security Threat Prevention" Id="{f995f849-a8a3-4467-8e46-1be14a1a358d}" DefaultIcon="True"><CompatibilityInfo BlockingType="Hard" StatusDetail="UpgradeBlock"/><Action Name="ManualUninstall" DisplayStyle="Text" ResolveState="NotRun"/></Program><Program Name="McAfee Endpoint Security Web Control" Id="{5cf878b6-6785-4369-b06b-693369855cfa}" DefaultIcon="True"><CompatibilityInfo BlockingType="Hard" StatusDetail="UpgradeBlock"/><Action Name="ManualUninstall" DisplayStyle="Text" ResolveState="NotRun"/></Program><Program Name="McAfee Endpoint Security Firewall" Id="{07b3d78c-8fc5-4de0-a873-09183826b715}" DefaultIcon="True"><CompatibilityInfo BlockingType="Hard" StatusDetail="UpgradeBlock"/><Action Name="ManualUninstall" DisplayStyle="Text" ResolveState="NotRun"/></Program><Program Name="McAfee Endpoint Security" Id="{116f9fe5-bc1f-41a6-998c-15e681d79902}" DefaultIcon="True"><CompatibilityInfo BlockingType="Hard" StatusDetail="UpgradeBlock"/><Action Name="ManualUninstall" DisplayStyle="Text" ResolveState="NotRun"/></Program></Programs></CompatReport>

Sean J Lehne

Monday, April 8, 2019 7:31 AM ✅Answered | 1 vote

Hi,

Yes, I think we have found that the McAfee is the faulty application and give setup the instruction to stop. 

**Please help check if the versions of the McAfee are different on these clients. **
And we could uninstall the McAfee on the problematic clients to have a try.

Please refer to:
McAfee support for Windows 10 Version 1809 (October 2018 Update) with upgrade from VirusScan Enterprise 8.8 Patch 9 to Endpoint Security 10.6.1

Hope my answer could help you. Thanks for your time.

Thanks and regards,
Simon 

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Thursday, April 4, 2019 4:29 PM

The 5 machines are 

  • 4 1709
  • 1 1703

One 1709 machine upgraded without any issues.

Sean J Lehne

Friday, April 5, 2019 1:23 AM

Its access denied by any-chance you have any AV?

Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights

Friday, April 5, 2019 7:18 AM

Hi Sean J Lehne,

Windows Setup failed with hexadecimal exit code 0xC1900208 (decimal 3247440392).

The 0xC1900208 error code could indicate that an incompatible app installed on your PC is blocking the upgrade process from completing. Please help check to make sure that any incompatible apps are uninstalled and then try upgrading again.

The first easy troubleshooting step we can do at this point is to launch setup.exe from the C:\WINDOWS.~BT directory. After going through the first screens, the setup will warn us about those incompatible apps.

If we don’t want to run the setup.exe, we can refer to the C:\WINDOWS.~BT\Sources\Panther\CompatData[date-time].xml. We’ll have a couple of Compatdata.xml files, usually, the most recent one will contain the information you need. Please check if there is a faulty application and give setup the instruction to stop.

For more detailed information, please refer to:
SCCM ERROR 0XC1900208 DEPLOYING WINDOWS 10 1709
Windows 10 Upgrade Setup Failed With Exit Code 0xC1900200

Hope it helps. Thanks for your time.

Best regards,
Simon Ren

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Friday, April 5, 2019 2:21 PM

I do have Mcafee, but it did work on 3 other machines that have the same configuration as the others that failed. Anything in particular that I would need to look for.

  • I have them folder exceptions set
  • C:\Windows\CCM
  • C:\Windows\CCMCACHE
  • C:\Windows\CCMSETUP

Sean J Lehne

Monday, April 8, 2019 4:46 PM

Yeah Looks like we had a older version of the client proxy out there on about 135 machines, We have updated the machines. Looks like once this is resolved we should be good thanks for the help!

Sean J Lehne

Tuesday, April 9, 2019 2:15 AM

Hi Sean,

Glad to hear that. Thanks for your feedback. I think the others who have similar issue will benefit from it.

Thanks and regards,
Simon

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].