Re: Group Policy errors with OEM installed "Small Business Server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

If that doesn't work... call PSS. You rebooted the box right?

Boxhill wrote:
Hi Frank,

Yes I've seen that and at first thought we were getting somewhere. From our UserEnv debug we deduced 8 locations with the rogue domain name and edited them all accordingly. It made no difference and upon re-running the debug they all still appeared addressing the rogue name. I must confess I hadn't tried this level of group policy editing before so it may be a lack of understanding on my part, but I did think I had got it right.

Many thanks for the thought,

Boxhill

"Frank McCallister SBS MVP" wrote:

Take a look at Merv's reply on http://support.microsoft.com/default.aspx?scid=kb;en-us;888943&sd=dell Make sure you have a GOOD backup before you edit that Bogus Domain name but that may fix your errors. Reboot after fixing.

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC
"Boxhill" <Boxhill@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F113EB6F-6077-4A72-8BFF-5623BCFFC68C@xxxxxxxxxxxxxxxx
Hi Susan,

I set up UserEnv debugging to see what was going on, details on this temp
link to our WEB site
http://www.zen21993.zen.co.uk/sbs_errors/first_debug_log.txt.

Actual error messages were:

error 1030
Windows cannot query for the list of Group Policy objects. Check the event
log for possible messages previously logged by the policy engine that
describes the reason for this.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

error 1005

Windows cannot connect to OEMSBSDN-2267.local domain. (Server Down). Group
Policy processing aborted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Any help truly appreciated, also thanks Frank unfortunately it's all well
and truly live, but lessons have certainly been learnt for the next time !!!

many thanks

Boxhill







"Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:

Can you give me a copy and paste of the errors?

Boxhill wrote:
We are getting "Group Policy failure" application log errors every 5 mins on
our brand new Server running a factory installed version of "Small Business
Server 2003". They log back to the moment we started the new system, but
unfortunately we did not start to investigate them until after spending a
couple of days installing it. We are getting event 1030 and 1005 which says
Windows cannot connect to OEMSBSDN-2267.local domain, group policy processing
aborted. Needless to say we have never used that name but trawling through
the debug logs we find one called "DCPROMO" dated 20/05/05 (10 months before
we bought the machine) which clearly indicates the software was indeed
originally set up with that name.

Looking through various forums, we are not alone with this problem, but no
one has come up with a satisfactory solution other than a clean reinstall,
which is a cost in time and money we would rather avoid and negates the whole
point of having SBS preinstalled by the OEM. Microsoft's article 888943
documents something similar and appears to imply it's the OEM's fault, which
we will be pursuing, however in the meantime if anyone has a way round this
we would be very grateful

Many thanks in advance, from one very frustrated IT guy !!!!




.

Relevant Pages

  • Re: Group Policy errors with OEM installed "Small Business Server
    ... Boxhill wrote: ... Windows cannot query for the list of Group Policy objects. ... our brand new Server running a factory installed version of "Small Business Server 2003". ...
    (microsoft.public.windows.server.sbs)
  • Re: Group Policy errors with OEM installed "Small Business Server
    ... Boxhill wrote: ... Windows cannot query for the list of Group Policy objects. ... our brand new Server running a factory installed version of "Small Business Server 2003". ...
    (microsoft.public.windows.server.sbs)
  • Re: User Profile Deleteion
    ... If you can't remove them manually, a reboot of the server could be ... you should be able to delete them and UPHClean ... MCSE, CCEA, Microsoft MVP - Terminal Server ... off.There is an option in Group Policy that does this well and ...
    (microsoft.public.windows.terminal_services)
  • Re: 1030 & 1058 errors
    ... station and on the server and compared the 1058 errors. ... I then used policy editor to recreate ... I ran the registry edit to make the change to 1 - did not work, reboot ... Windows cannot query for the list of Group Policy objects. ...
    (microsoft.public.windows.server.sbs)
  • Re: Group Policy errors with OEM installed "Small Business Server
    ... "Frank McCallister SBS MVP" wrote: ... "Boxhill" wrote in message ... Windows cannot query for the list of Group Policy objects. ...
    (microsoft.public.windows.server.sbs)