AlbinoRaven

Reset the TCP stack. http://support.microsoft.com/?kbid=299357 Reboot and done. I've found in some customers PC where they have gone from a dialup stack to DSL NIC, things are good. Where it gets weird is going back from DSL to Dialup. Reset the stack and make sure you've pulled the nic BEFORE the stack gets reset. For some reason it wants to only reset the NIC stack if both pieces of hardware are present. You mean you haven't had it YET. My favorite is when the daily updates hit and don't finish the compile properly. Suddenly you've got a half compiled driver, a kernel dumping all over the place and all you can do is pray for a good backup. You should check out the noise that is made by some of the linux distros, especially the ones people pull off the torrents. Nothing but rootkits. In fact most of the zombie spam comes from all of those "official" releases because people just compile their own pieces into them and drop them in the torrents. The torrent weights the seeds and puts it at the top of the list. Volia instant rootkit zombie linux army and because most people don't verify they stay oblivious to that fact "all their base are belong to *someone else*" If you bought the linux title at the store or verified it's same MD5 hash from the real vendor, it's legit. If not, better start running the decompiler and looking for the nasty. After all the term root kit comes fromt he *nix side of the universe. When it happens on windows it's because the RIAA wants to catch piracy, when it's done on *nix, it's usually for "other" reasons.

That would do it.

What is your Tombstone set at? As in, how long AD keeps a record of a server before it nuked. I have mine set to 45 days. If I remove a server from the domain, in 45 days all of the domain controllers understand that they will delete the server entry for the server I removed from the server. Otherwise you have to nuke the server manually from the OU and make sure you are doing it from the domain controller that maintains the FISMO roles.

I remember seeing one YEARS ago on SNMP.org in the downloads section. Simple vbs script as I recall, it was for win2k though. Doubt it'll make a big diffence but you never know.

Exactly. Or if the system you want to ghost is another box. You can ghostcast the server over the network.

Yup, Use ghost 8 or better and if you're doing deployments double check that the syspreped server does what you need it to before using ghost's mutlicast feature. OR do you just want to make a backup? Never know...

Is the clipboard service running. If not, turn it on and try Cut/copy/paste.

I've used the USMT (User State Migration Tool) from microsoft. It seems to work fine, just don't get the new version that microsoft is offering. Best Bet is USMT 1.2 Otherwise It'll complain that you are migrating to Windows 2003. Or if you are doing a huge migration, try using the fastlane migration suite (http://www.quest.com/migration/). Expensive but worth every penny if you need to have a couple hundred servers done in a day so long as the staging is done properly.

Couple of things Is the SNMP service installed? Is the SNMP service set to automatic and enabled? Is the builtin Windows 2003 SP1 firewall have an exception so SNMP can pass out the network card? it's disabled by default. So if the first two thigns are okay, check the firewall config. You can have a specific community string but the public should work just fine to get the mib trunk of 1.3.6.1.X. It will load without errors and show the mib root when you are walking it with something like mibwalker.

It's there in Windows 2000, it's the imaging tool. I think you have to add it in the add/remove components section under accessories.

It's because the DNS service is still running. Stop the service, disable it, reboot, flush entries, set to automatice and reboot again. DNS administration assumes that you have a secondary DNS server running somewhere. On the one that you want to flush, shut down the service and then run the admin tools to get rid of the old dns entries.

You're looking for AD intergration? Ummmm, most of the other mail server packages that are out there do SOME type of hook to Active Directory with LDAP. It's a real b***h though trying to get the LDAP setup properly and stable though and it only reads Active Directory as a list of contacts. It won't dynamically create the email account unless you've done some heavy scripting to automate that task. As far as how to script the account creation automation. It really depends if the mail server package offers that. Trust me, if you have the money to spend on Exchange 2000 or greater. Do it. The other way is a nightmare.

Just noticed that you've got a $OEM$ under your i386 directory. The $OEM$\$1 directory has to be on the root. Nothing goes under the i386 directory. If you want something to copy stuff into the winnt directory you use the following. Cheers! \$OEM$\$$ Contains files that Win2K Setup copies to the %Windir% (e.g., C:\winnt) folder during installation. \$OEM$\$$\Help Contains custom Help files that Win2K Setup copies to the %Windir%\Help folder during installation. \$OEM$\$$\System32 Contains custom Help files that Win2K Setup copies to the %Windir%\System32 folder during installation.

I just answered this for another lad in an other thread. http://www.msfn.org/board/index.php?showto...mp;#entry524651 Cheers!

Perfect. There are some other switches with install shield but I find they are kinda pointless unless I'm debugging one of my own Install shield compiles. /r and /s are our friends.