none
Event ID 1202 SceCli 0x4b8

    Pertanyaan

  • I have a 2008 R2 Standard terminal server farm.  They are all VMs in ESX.  I just deployed 3 new servers from a template and I am getting Event ID 1202 Source SceCli Security policies were propagated with warning.  0x4b8: An extended error has occurred. 

    I get this each time I log in.  I haven't opened this up to my clients yet since I am getting this message.  None of the other servers in my farm give me this message.  I have deployed other servers from the same template.

    Kamis, 21 April 2011 21.16

Jawaban

  • Have a look to this Microsoft article about troubleshooting Event ID 1202 SceCli:

    http://support.microsoft.com/kb/324383

    Search for 0x4b8 in the article>


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Kamis, 21 April 2011 21.44

Semua Balasan

  • Have a look to this Microsoft article about troubleshooting Event ID 1202 SceCli:

    http://support.microsoft.com/kb/324383

    Search for 0x4b8 in the article>


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Kamis, 21 April 2011 21.44
  • Terrible answer.  The article applies to Windows 2000 and further the SECEDIT command is not the same between 2000 and 2008.  Please either link a relevant article to Server 2008 or update the current article to reflect modern technology.
    • Diedit oleh crashIO Rabu, 14 Desember 2011 16.36
    Rabu, 14 Desember 2011 16.36
  • Did you ever resolve this one?
    CarolChi
    Rabu, 25 Januari 2012 17.09
  • Terrible answer.  The article applies to Windows 2000 and further the SECEDIT command is not the same between 2000 and 2008.  Please either link a relevant article to Server 2008 or update the current article to reflect modern technology.

    The answer isn't terrible. A lot of the core information of the link still applies to 2008/2008R2 in this instance. Of course it should be understood that there will be some differences between the two operating system versions, some of which are well known - like that you now use gpupdate instead of secedit to refresh group policy. If someone doesn't know the new way to do something mentioned in an article, they can comment and will likely receive help. Bashing an answer that contains good information just because there are some small idiosyncrasies lends nothing toward helping the OP, or anyone else that comes across this thread, resolve their issue. It's much better to be a helpful member of the community.

    In my case with this issue, it was caused by someone creating a local account on a 2008 R2 server with the name that is used for renaming the built-in administrator account by our domain-based security group policy. This cause is detailed in a sub-link under the link posted above: http://support.microsoft.com/kb/260715/EN-US. Once the account was removed, a gpupdate processed without issue and the error went away.

    Minggu, 12 Februari 2012 00.26
  • Same here. Turned out to be a local policy to rename the administrator account into an existing username.

    "Please contact your administrator..." :-(

    • Disarankan sebagai Jawaban oleh nujjo Selasa, 05 April 2016 17.48
    Kamis, 02 Agustus 2012 11.33
  • Yeah, idk how that answer got voted the solution.  I can't stand it when people just copy and paste the first thing they google...and he knows that's exactly what he did.  From start to finish, the steps defined for pretty much every error (at least the ones that applied to me) were completely useless.  If you complain then you get people like the previous guy that defend them like, "He's just trying to help.  If you bash answers you won't get any help, blah blah blah.  It's not help when you just waste people's time.  Did the crap in the registry and did the command only to realize it was for an operating system nobody has used in like 7 years.  Would have rather not even had a response.
    Selasa, 27 Januari 2015 16.41
  • This resolved my issue.  There was indeed a local account with the same name as the "renamed" domain admin account.  

    Thanks!

    Selasa, 18 Agustus 2015 12.47
  • Same thing for me. We change the Administrator name with Group Policy. However, I manually set up my computer and created the default account with the same name, so Group policy was failing to change the Administrator account name. Deleted the local account and let GP do it's thing and the error went away. Windows 10.
    Selasa, 05 April 2016 17.50
  • because it was the right answer for the issue. if you dont have the ability to use your own "googlers" and find a workable solution, or dont have the knowledge to understand how 2000 and 2008R2 are similar in many many ways(just changed the names of some features) then i would just shut up and sit down. trying to call out another tech for not giving you the absolute answer is just making YOU look like an idiot. SECEDIT=GPUPDATE how hard is that to understand? the registry mapping hasnt changed since they started producing windows server.... also instead of using the recommended "third party" software to change the ACL's you can use the newer "SUBNACL" which does the same exact thing. nobody is ever going to just hand you a 100% answer.
    Rabu, 13 April 2016 16.54