Jump to content


FromTheUnderground

Established Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About FromTheUnderground

  • Rank
    Newbie
  • Birthday 11/12/1982

Profile Information

  • Gender
    Male
  1. My only experience with USMT is through SCCM. The command was built through Task Sequence. Is there anything in particular I need to look for?
  2. Hey everyone. I have having some difficulties troubleshooting a USMT restore Task Sequence. I have a computer that is already image and needs a user's data migrated to it. I have already created the computer association and when I view the recovery information, everything looks good. The problem is when I deploy my TS, as soon as the Restore User State starts to initialize, it fails with code 0x8007000B. Below is the Loadstate log. Any help would be greatly appreciated. 2014-12-15 15:55:34, Info [0x000000] LOADSTATE.EXE Version 6.3.9600.17029[gle=0x000000b7] 2014-12-15 15:55:34, Info [0x000000] USMT Started at 2014/12/15:15:55:34.689 2014-12-15 15:55:34, Info [0x000000] Command line: C:\_SMSTaskSequence\Packages\PS100098\amd64\loadstate.exe \\sccmprdps01.dmd.gsuad.gsu.edu\SMPSTOREF_FB8710A0$\745CE4E49B9D971C308FA33A7320D3145F128CFD0677C301C72410B04A9AC35D /decrypt /keyfile:**** /ue:*\* /ui:DOMAIN\user /lae /lac:password /v:5 /c /l:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstate.log /progress:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstateprogress.log /i:C:\_SMSTaskSequence\Packages\PS100098\amd64\migdocs.xml /i:C:\_SMSTaskSequence\Packages\PS100098\amd64\migapp.xml 2014-12-15 15:55:34, Status [0x000000] Activity: 'MIGACTIVITY_COMMAND_LINE_PROCESSING' 2014-12-15 15:55:34, Info [0x000000] Failed.[gle=0x00000006] 2014-12-15 15:55:34, Info [0x000000] An error occurred processing the command line. Undefined or incomplete command line option[gle=0x00000006] 2014-12-15 15:55:34, Info [0x000000] USMT Completed at 2014/12/15:15:55:34.691[gle=0x00000006] 2014-12-15 15:55:34, Info [0x000000] Entering MigShutdown method 2014-12-15 15:55:34, Info [0x000000] Leaving MigShutdown method 2014-12-15 15:55:34, Info [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------[gle=0x00000006] 2014-12-15 15:55:34, Info [0x000000] * USMT error code 11: [gle=0x00000006] 2014-12-15 15:55:34, Info [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006] 2014-12-15 15:55:34, Info [0x000000] | An error occurred processing the command line.[gle=0x00000006] 2014-12-15 15:55:34, Info [0x000000] | Undefined or incomplete command line option[gle=0x00000006] 2014-12-15 15:55:34, Info [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006]
  3. Hello all. I am running into multicast issues and looking for some help. Current system: SCCM 2012 R2 Cumulative Update 3 (5.0.7958.1401) with 1 site server, 1 db server, and 1 distribution point. I have a task sequence to push out an image via multicast but on the client computer I keep getting error number 80070002. The DP is set to enable multicast, all the contact within the task sequence is located on the DP and all packages are set to "allow this package to be transferred via multicast." I read a few places that turning off multicast support on the DP for an hour then turning it back on would correct the issue. This is a copy of the log file after doing so. Notice the Error finding namespace entry in the log. Any help and suggestions would be greatly appreciated. Thank you. Josh Multicast error file: Setting WDS IpAddressSource McsExec 11/21/2014 1:38:51 PM 5088 (0x13E0) Running: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:51 PM 5088 (0x13E0) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:51 PM 5088 (0x13E0) Run completed for: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:52 PM 5088 (0x13E0) Running: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:52 PM 5088 (0x13E0) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:52 PM 5088 (0x13E0) Run completed for: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Succesfully Configured WDS McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Error finding namespace McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Checking MCS Certificate McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) MCSEncryptionCert Created. Length 980. McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Setting WDS IpAddressSource McsExec 11/21/2014 1:38:55 PM 2468 (0x09A4) Running: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:55 PM 2468 (0x09A4) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:55 PM 2468 (0x09A4) Run completed for: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:56 PM 2468 (0x09A4) Running: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:56 PM 2468 (0x09A4) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:56 PM 2468 (0x09A4) Run completed for: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:57 PM 2468 (0x09A4) Succesfully Configured WDS McsExec 11/21/2014 1:38:57 PM 2468 (0x09A4) Setting WDS IpAddressSource McsExec 11/21/2014 1:43:36 PM 4924 (0x133C) Running: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:43:36 PM 4924 (0x133C) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:43:36 PM 4924 (0x133C) Run completed for: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:43:37 PM 4924 (0x133C) Running: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:43:37 PM 4924 (0x133C) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:43:37 PM 4924 (0x133C) Run completed for: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:43:38 PM 4924 (0x133C) Succesfully Configured WDS McsExec 11/21/2014 1:43:38 PM 4924 (0x133C) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:43:53 PM 4244 (0x1094) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:43:53 PM 4244 (0x1094) Error finding namespace McsExec 11/21/2014 1:48:53 PM 3328 (0x0D00) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:48:53 PM 312 (0x0138) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:48:53 PM 312 (0x0138) ========== HashAndSignBuffer McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== OpenSession McsExec 11/21/2014 1:52:19 PM 312 (0x0138) Error finding namespace McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== OpenSession -- exit code: 0xc1100113 McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== HashAndSignBuffer McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== OpenSession McsExec 11/21/2014 1:52:20 PM 312 (0x0138) Error finding namespace McsExec 11/21/2014 1:52:20 PM 312 (0x0138) ========== OpenSession -- exit code: 0xc1100113 McsExec 11/21/2014 1:52:20 PM 312 (0x0138) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:53:53 PM 312 (0x0138) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:53:53 PM 312 (0x0138)
  4. I found a solution that works for my environment. I created a collection "All Imported Systems" that lists all computers that have been manually imported. I then created a collection for each of our area admins (based on OU permissions within AD) and created a security role specifically to these newly created collections. I got the idea from Michael Lucero - Austin from another forum. "Here is a solution that should work for you. Perform this on a test account with only the security role you are going to change for your users in question. Create a new collection that is a copy of your collection limiting collection mentioned above. Set the limiting collection of this new collection to something other than the limiting collection it defaults to, which is the copied collection. Select the collections to which you wish to grant Add Resource permissions to and set their limiting collection to this new collection. Within your Administrative user or group properties, specify this new limiting collection and the collections you wish to allow Add Resource permissions under the "Associate assigned security roles with specific security scopes and collections - don't forget to add your security scope. Apply the changes and test - don't forget to restart the console of your test account. This does a couple things - it allows the Add Resource function to the specific collections you wish for the specific Administrative user/group you wish. It does NOT allow modify on the limiting collection. And it separates the specific collections you tag as being modifiable by the specified group. We had the same issue in our environment - need a specific group to be able to Add Resource to a single specific collection which was being limited by the All Workstations collection. Allowing modify to the All Workstations collection allowed modifications to any collection limited by All Workstations. So I came up with the solution above, tested against my test accounts and it works as I needed. Hopefully this will solve your issue and give you some options going forward."
  5. I am looking for some assistance with security permissions on device collections. We have several small IT departments that manage their own computers all connected into our primary AD domain and SCCM site. I currently have device collections with their limiting collection as "All Systems" built out pointing directly to each distributed IT department's Active Directory OU. This allows the distributed IT admins full control over their machines within their AD OU, but prevents them from seeing or managing computers in another department's AD OU. The issue I have run into is I want to allow each of these groups to manually import computers using a csv file for bare metal deployment. In our environment, we cannot enable deploying to unknown computers. I have created a collection off of All Systems called "All Imported Systems" that lists all systems that were manually imported. Is there a way I can allow all users read access to this collection AND be able to use this collection as the limiting collection? I have parts of this completed but I think I am missing a step somewhere. OR If there is a way to give a group the ability to manage the membership of a collection without giving them the ability to change the limiting collection. Let me know if I need to supply any more information on the environment or what I am trying to accomplish. Thank you all in advance. Josh
  6. The update I applied that resolved my issue was KB2965445 "Update Rollup 3 for MS System Center 2012 R2 - Operations Manager Server"
  7. I think I have it working now. Under further investigation, I found there was a SCOM update that had not been applied yet. Once I installed that update, all my 2012 R2 servers started getting monitored. Thanks for your help with this.
  8. Hi AdinE, I tried the steps you mentioned and all the folders were recreated when I stared the Agent service again. Still the machines show as No Monitored. I decided to do some more tests and found that I am only having this issue with systems running Server 2012 R2. All other systems, Server 2008, 2008 R2, and 2012 all connect up and are monitored without any issues. I verified the 2012 R2 management pack was imported and available.
  9. I am taking over an instance of SCOM 2012 R2 and running into issues when trying to add new machines to monitor. I go through the Discovery Wizard and choose the specific machines I want to monitor. The agent gets installed; I confirmed this by logging into each of the machines. After the agent is installed, the Health state stays at Not monitored. When I run Get-SCOMAgent in Powershell, those same machines show Uninitialized under the HealthState column. The machines were added roughly 15 hours ago. Am I missing something? Are there specific things I should be looking for in the log files? Thanks in advance.
×
×
  • Create New...