Do not change it based on what DCDIAG says unless you are running the version of DCDIAG that goes with that OS (this is where much of the Internet got confused on causality versus correlation). It’s expected and normal for this service’s behavior type to be 0x10 on Win2003 and 0x20 on Win2008 and later. Do you know why this is different and what’s going on? It looks like the difference is being a service in a shared versus isolated process. That say I should change the value using theĬommand. WIN32_OWN_PROCESS, expected value WIN32_SHARE_PROCESS Invalid service type: RpcSs on DC01, current value It tells me the Windows Server 2003 DCs are failing a service test around RPCSS: I have a mixed environment of Win2003 and Win2008 DCs. Profile conversion from workgroup to domain joined computers MIGAPP.XML compatibility between USMT 3.01 and 4.0 Today we talk DCDIAG, DFSN, DFSR, group policy, user profiles, migrations, USMT, and the fuuuuuuturrrrrrrrre. First published on TechNet on Feb 11, 2011
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |