|
Al I wish I had that luxury. I do
consulting. Most of the time I am looking at an AD environment because
the customer realizes it is a complete mess, and my job is to clean it up and
walk away. If they were willing to do it as you described, I would
probably not need to be involved in their network. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Al Mulnick Kevin, as someone who is currently living a similar situation, I
personally decided that there should no solution out there that I am
responsible that cannot be restored in a repeatable way. It's a lot of
extra work, but one by one I go through each application (in order of stated
importance) and restore them to the lab environment until working as declared
by the business application owner. I document each step. I make sure I
know where each piece of software is. I make sure I have what's needed to
put it back together. I try to catch some sleep in between at some
point. I laugh at the weekends... wait, that's off-topic. Anyway, if you
have any other apps like that, and it's likely that you do, I think it's in the
best interest if you ensure that restoration procedures and documentation are
up to date and tested. I realize what a tremendous amount of extra work that is
with seemingly little tangible return. Similar to accident insurance,
you really don't see the benefit until you need it. It's worth the time to go through each of the apps. Besides, you
might be surprised at what you find and at how much easier each day after that
becomes. Again, my $0.04 worth (all money values stated are USD unless otherwise
mentioned)
On 7/17/06, Certainly the biggest problem I have come across upgrading
from 2k to 2003 was because of one of these legacy settings. I don't know
who at MS decided to go from "WINNT" to "Windows",
but it can cause some pretty serious recovery issues if you are not using some
sort of bare metal restore. Here's the scenario: You've got a server with some critical piece of
software. Because you don't know anything about the software and it was
the last admin that installed it you decide to upgrade instead of clean
install. This leaves Win2k3 running out of the WINNT folder instead of
the Windows folder. After a few months, the server loses a RAID card,
corrupting the disk set, and it needs to be back up immediately. You
begin a fresh load of 2003 on the server, and then notice that it is installing
to Windows, not WINNT. After the fresh load finishes, you try to restore
the last backup. BSOD. Hmm, how do you make Win2k3 install to
WINNT, oh yeah that's right, you don't. Now instead of restoring the last
backup and system state and moving on with life you are installing the apps
from scratch and hoping they work right. Perhaps after a long weekend it
is back up again, but it shouldn't have been that hard. Too bad the
last admin who worked here didn't leave any sort of documentation on how this
thing works. Sure, you're running all of your servers virtual so this
doesn't apply to you. Bare-metal restore, no big deal. Restore from
tape or file, good luck. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of joe I agree with Jorge on this. Every new OS MSFT comes out with
they tell you that it is much better at handling upgrades than the last and how
bad the last one actually did it. So if someone tells me K3 does it great I
tell them to say that when say LongHorn comes out. :) Anyway, you will have legacy settings that stay around when
you do an upgrade say like the replication holdback reg settings, etc when you
do an upgrade and it could be confusing later when troubleshooting something. Unless there is absolutely no way possible to do a fresh
install then I would recommend going that way. Going slightly OT, I even reinstall my personal home clients
on a regular basis (normally every 6 months but occasionally that slides
depending on how busy I am) to get away from Windows rot and clean off
crap that I don't currently use. I am also getting big into using virtual
machines for most desktop functions now so that makes things even easier as I
can roll back to a predetermined point or just pull the backup image off of a
DVD that I made when I first made the image. Of course make sure you update the
image with new patches first thing. :) In fact right now, I am
writing this email on a virtual XP instance running with about 15 other
virtuals on a machine that is on the other side of
my house. Also all web surfing to untrusted sites is done
through a virtual I have with undo disks, after I finish surfing I tell it to
undo and it is ready for the next time. -- O'Reilly Active Directory Third Edition - http://www.joeware.net/win/ad3e.htm From: [EMAIL PROTECTED]
[mailto: [EMAIL PROTECTED]]
On Behalf Of Almeida Pinto, Jorge
de Personally I hate OS upgrades and try hard to
avoid them and prefer to choose a fresh clean install... Although
supported when upgrading an OS old stuff from the previous OS is kept and
besides that you might run into issues because of incompatibilities with
software, drivers, etc. A clean install in combination the migration of the stuff
hosted on the old server to the new server gives you a phased approach.
Upgrading directly impacts the server and if the upgrade fails you might end up
with a trouble server. IMHO: *
avoid OS upgrades when possible and only use it when really necessary (like for
example NT4 PDC -> W2K3 DC, which is mandatory) Met vriendelijke groeten / Kind regards, Ing. Jorge de Almeida Pinto Senior Infrastructure Consultant MVP Windows Server - Directory Services LogicaCMG Nederland B.V. (BU
RTINC ( Tel : +31-(0)40-29.57.777 ( * E-mail : <see sender address> From: [EMAIL PROTECTED]
on behalf of Bahta, Nathaniel V CTR USAF NASIC/SCNA Hey all, Does anyone have any comments/articles, etc on the benefits
or concerns of a clean install of Windows 2003 Server VS an Upgrade? My
opinion is that doing a clean install keeps system root clean. It also
pristinely adopts the security best practices of 2003 Server. Disk
performance will improve as well. Does anyone have anything they can add
to this? I have migrated a great portion of my network in a clean install
path, and now it is coming into question why did I not choose the upgrade path.
Any comments would be greatly appreciated, Thanks, Nate |
- Re: [ActiveDir] Clean inst... Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
- RE: [ActiveDir] Clean inst... joe
- RE: [ActiveDir] Clean... David Adner
- Re: [ActiveDir] C... Al Mulnick
- RE: [ActiveDi... joe
- RE: [ActiveDir] C... joe
- RE: [ActiveDir] Clean inst... Peter Johnson
- RE: [ActiveDir] Clean inst... Kevin Brunson
- Re: [ActiveDir] Clean... Al Mulnick
- RE: [ActiveDir] Clean... joe
- RE: [ActiveDir] Clean inst... Kevin Brunson
