Windows

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
Home » Development Group »» Windows
  • GPO wierdness during forest migration

    0 answers - 1364 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg

    Nicolas-
    I hope things are well in SA. So, one possible issue here could be in how
    the machines have been moved between forests. Were they re-imaged or just
    moved between domains? If the latter, then what you could be experiencing is
    some crap (technical term) in the registry from the old domain that
    effecting GP processing. I would look under the Policies keys in HKLM and
    HKCU for a given user and see if the stuff referenced in there is old or
    new.
    Not sure why ADMT would be any different however.
    Darren
    Message
    From: ActiveDir-owner (AT) mail (DOT) activedir.org
    [mailto:ActiveDir-owner (AT) mail (DOT) activedir.org] Behalf Nicolas Blank
    Sent: Monday, May 15, 2006 11:26 AM
    To: ActiveDir (AT) mail (DOT) activedir.org
    Subject: [ActiveDir] GP wierdness during forest migration
    Hi all
    Migrating from one forest into another, one way trust treating the source as
    a resource forest.
    Migrating using Quest Migration Manager with Sidhistory.
    Weird thing is that on the users machine, gpresult gives me source and
    target GP's as applied, however target GP's are applying inconsistently in
    practice - i.e. script firing sometimes.
    If I migrate with ADMT, this behavior does not follow.
    Anyone ever seen anything like this before?

Re: GPO wierdness during forest migration


max 4000 letters.
Your nickname that display:
In order to stop the spam: 4 + 3 =
SPONSORED
QUESTION

SPONSORED
EMSDN