Jump to content


dylan_s

Established Members
  • Content Count

    11
  • Joined

  • Last visited

  • Days Won

    1

dylan_s last won the day on January 23 2012

dylan_s had the most liked content!

Community Reputation

2 Neutral

About dylan_s

  • Rank
    Member
  1. Ok. I found the C:\SMSTSLog folder with more info Hash errors on the download of the Windows image file: Successfully connected to "servershare\dp\smspkg\LMC0017A" Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' Hash could not be matched for the downloded content. Original ContentHash = 7862B09EC00AA6A5FA8719E439EE38931B1CDC98, Downloaded ContentHash = 50E19DA457463029738D3E2F23FC69AFA6AAFDFC Installation of image 1 in package LMC0017A failed to complete.. The hash value is not correct. (Error: 80091007; Source: Windows) Failed to run the action: Apply Operating System. The hash value is not correct. (Error: 80091007; Source: Windows) So I've already refreshed this package on the DP with the exact same results. Any suggestions?
  2. That's exactly what I did. Sorry I did not get back to the thread to clarify.
  3. I have an environment with two 2007 R2 SCCM servers (primary and secondary) along with a third site that has a server share DP. We are running OSD & PXE boot deployments at the sites with SCCM servers. I would like to run OSD (PXE boot deployment not necessary) at the site with the server share DP. All of my task dependent packages, driver packages, boot images and Windows images are on the site 3 DP. Is it possible to run OSD tasks from the server share DP in this environment? When I attempt to run an OSD task on a PC at the third site it: launches the task downloads the USMT for profile scan captures the windows settings specified in the task sequence downloads the boot image restarts fails to download the windows image I'm using a PC model that can successfully run OSD and PXE tasks at site 1 and site 2, so I know that the boot image has the necessary hard disk and network drivers. No partiton issues either. smsts.log
  4. I had the same problem with the NVS4200M and NV300 drivers in my driver packages used in our OSD task. My solution was to create a seperate package with the extracted Nvidia install components and execute that as a Install Software task near the end of my task sqeuence. Command: setup.exe /s /n /noeula /nofinish
  5. I have a DHCP server and SCCM server with WDS configured as a PXE boot point on SUBNET1 PXE boot clients on SUBNET1 receive an address and PXE boot, download images, etc PXE boot clients on SUBNET2 do not receive a DCHP address No router in the mix, all VLANs in this example are configured on a Cisco 2975 switch stack (no hop/router between SUBNET2 and the DHCP server). I have already enabled spanning-tree portfast trunk on the SUBNET2 client port with no change. Any ideas?
  6. Just to follow up and post the full file that successfully migrates the folders & files as intended in case anyone is looking to do something similar. <?xml version="1.0" encoding="UTF-8"?> <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/migautodesk"> <component type="System" context="User"> <displayName _locID="miguser.Autodesk">Autodesk</displayName> <role role="Settings"> <detects> <detect> <condition>MigXmlHelper.DoesObjectExist("File","%CSIDL_APPDATA%\Autodesk")</condition> </detect> </detects> <rules> <include filter="MigXmlHelper.IgnoreIrrelevantLinks()"> <objectSet> <pattern type="File">%CSIDL_APPDATA%\Autodesk\* [*]</pattern> </objectSet> </include> <locationModify script="MigXmlHelper.RelativeMove('%CSIDL_APPDATA%','%CSIDL_LOCAL_APPDATA%')"> <objectSet> <pattern type="File">%CSIDL_APPDATA%\Autodesk\* [*]</pattern> </objectSet> </locationModify> </rules> </role> </component> </migration>
  7. I think this: <include filter="MigXmlHelper.IgnoreIrrelevantLinks()"> <objectSet> <pattern type="File">%CSIDL_APPDATA%\Autodesk\* </pattern> </objectSet> </include> Should be: <include filter="MigXmlHelper.IgnoreIrrelevantLinks()"> <objectSet> <pattern type="File">%CSIDL_APPDATA%\Autodesk\* [*]</pattern> </objectSet> </include> ....missing [*]
  8. Problem solved: duplicate urlid (DOH!) Changed the urlid and successfully migrated my Autodesk folders (but not the contents) to the appdata\local One problem down and a new one to sort out.
  9. I have a hardlink USMT task sequence running successfully with my OSD from SCCM. We have a couple dozen AutoCAD users and I would like to add a custom XML to migrate their custom settings from C:\documents and settings\username\autodesk\* to C:\user\username\app data\local My custom xml causes the restore task to fail: <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/custom"> <component type="System" context="User"> <displayName _locID="miguser.Autodesk">Autodesk</displayName> <role role="Settings"> <detects> <detect> <condition>MigXmlHelper.DoesObjectExist("File","%CSIDL_APPDATA%\Autodesk")</condition> </detect> </detects> <rules> <include filter="MigXmlHelper.IgnoreIrrelevantLinks()"> <objectSet> <pattern type="File">%CSIDL_APPDATA%\Autodesk\* </pattern> </objectSet> </include> <locationModify script="MigXmlHelper.RelativeMove('%CSIDL_APPDATA%','%CSIDL_LOCAL_APPDATA%')"> <objectSet> <pattern type="File">%CSIDL_APPDATA%\Autodesk\* [*]</pattern> </objectSet> </locationModify> </rules> </role> </component> </migration> Any feedback would be appreciated.
  10. I now have this narrowed down to happening only on certain machines. They were failing the OSD task at the Request User State Storage, so this was prior to any physical changes on the PC. After the failed OSD task, the agent status was changing to Inactive and Obsolete when I viewed the properties in the OSD collection. Repairing/reinstalling the agent appears to resolve the issue. I'm not sure why this is happening though.
  11. Backround:SCCM 2007 v. 4.00.6487.200 build 6487 R2 Installed I was experiencing the issue with my USMT referenced in KB977203. Attempted to install the hotfix from the KB & it hosed up my MP on my primary and secondary site due to some odd permissions issue with the c:\windows\tasks folder & stopped distributing packages all together. Opened at support ticket w/ Microsoft, uninstalled the hotfix from add/remove & wound up reinstalling the MP. A couple packages needed to be deleted and recreated to work after. Now.... I have clients fail the task becuase it can't find the xml files for the USMT sequence. Fine, I'll build a new package and rerun the task. Problem: *Any client that ran the OSD and failed the 1st time immedately goes to "The requested software cannot be located" on second attempts smsclui.log: Could not find the policy in WMI for package program Suggestions?
×
×
  • Create New...