Hi Dan,
Thanks for the pointer! I downloaded that MS document a long time
ago and I think I was so overwhelmed by the content, I didn't even see
the modified delegwiz.inf that was presented in Appendix O . Thanks
again for the pointer; it's going to be a big help in developing future
delegations.
Mike Thommes
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan Holme
Sent: Friday, May 20, 2005 12:13 PM
To: [email protected]
Subject: RE: [ActiveDir] delegwiz.inf file replaced with w2k3/sp1
upgrade
I've done a lot of Delegwiz.inf customization and to my experience do
not believe there's a way to avoid what you experienced. The only
workaround is a cheesy one. I have a workflow for post-SP "repairs" --
a share where I keep anything that needs to be 'replaced' after an SP.
BTW, I assume you've seen the Appendices to the Active Directory Best
Practices? The Delegwiz.inf file in there rocks as a starting point.
http://tinyurl.com/e3n2u
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jorge de
Almeida Pinto
Sent: Friday, May 20, 2005 9:11 AM
To: [email protected]
Subject: RE: [ActiveDir] delegwiz.inf file replaced with w2k3/sp1
upgrade
I think not...
What I would do:
* Rename the default DELEGWIZ.INF to DELEGWIZ-SPx.ORG (where x is the
service pack number)
* Create my own DELEGWIZ.INF (or customize the default) and create a
copy
called DELEGWIZ.INF.CUSTOM
Implement the custom DELEGWIZ.INF on all DCs that are used to configure
delegation, and do the above only on one DC (like the PDC FSMO for
example)
Cheers
#JORGE#
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thommes,
Michael M.
Sent: Friday, May 20, 2005 17:52
To: [email protected]
Subject: [ActiveDir] delegwiz.inf file replaced with w2k3/sp1 upgrade
We discovered today that our custom delegwiz.inf (the input file for the
delegation GUI) was replaced during the upgrade from w2k3/sp0 to
w2k3/sp1.
8-( Luckily, we do have backups. 8-) Anybody ever caught up in this
issue? Files likely to be customized by MS customers should be handled
with
"kid gloves" by MS during standard upgrades. Is there some way to
designate
another location so we don't get surprised again?
Thanks!
Mike Thommes
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be
copied, disclosed to, retained or used by, any other party. If you are
not an intended recipient then please promptly delete this e-mail and
any attachment and all copies and inform the sender. Thank you.
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
