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.

Sorry all of the formating I did was nuked so the message definately got muddled. It should be <CD ROM>\$OEM$\$1\Myfolder <CD ROM>\i386 That's it. Are you using nLite to compile the iso or are you using WinISO like a file manager? I find that Win2K3 something works better after running it in the nLite iso creator. It'll even give you the options of picking folders from your local drive and creating the $OEM$\$1 dir structure.

Well VMware Esx uses a product called P2V (physical to Virtual). As far as the microsoft work around it's kinda annoying, but it can be done. You use ghost to capture the snapshot of the drive to your *.gho file. Used ghost to create a bootable diskette. Get a full copy of WinISO and create a bootable CD using the ghost bootable diskette you've made. Or go to bootdisk.com and copy ghost into the disk. Next copy the *.gho file into the Bootable cd iso you made with WinISO. Make sure that ghost is on there. Now Mount the iso as your "CD" in the virtual machine and boot. Ghost the VM disk as you normally would on the VM. Cheers!

YOu don't have to assign letter C for the first drive. If you force a format it will do that for you automatically and in theory copy your files to the drive afterwards.

The root directory structure should look like this: <CDROM> \$OEM$ \$1 \MyFolder \i386 Caps do matter for the $OEM$ I'm using Win2K3 Enterprise. Basically the same as Standard.

For installshield you have to first record the installation that you want with the /r switch. For my example I'll a monitoring agent I use on my servers called eGagent. It has a setup.exe. I open a command line window and navigate to the directory with the agent and use the following to start the process of recording the iss file. example: setup.exe -r -f1"c:\eG\eGsetup.iss" This will launch the setup application and you select the options you want and they get recorded to, in my case, c:\eG\eGsetup.iss and record a log file in case I messed up. Then if you want to silently install the application you use example: setup.exe -s -f1"c:\eG\eGsetup.iss" That's it. Hope it works out.

Not yet but it looks like some of the other groups I do work for are interested in doing that. I'm building an autoinstall for one of our web apps in our web farm. The first drop for it was the unattended methods for CD building, took about a month and bit to get it done right. The WinPe method is going to allow me more control over the disks as there isn't any way to monkey with disk partitioning properly with unattended CD without using a third party. Plus I thought it would be cooler looking. The debug command works great BTW. Thanks

Nuts! I totally forgot about that. I'll add this to my diskpart script: list disk select disk 0 delete disk 0 list disk select disk 0 create partition primary assign letter c exit I'll give this a shot too.

Hi all, I've thumbed through the newsgroups, microsoft's "help" files and did a little bit of roaming through here. I've been trying to take my unattended win2k3 sp1 build and "plop" it into WinPE 1.1 and run the setup with PE as the Drive config tool. So far with trying things I've seen here I can get it to start the minint setup, but all it seems to do is tell me it's 50 minutes, reboot and boot back into WinPE. Basically it hasn't made the C drive bootable or copied the setup files over. Makes me sad. At least I'm running VMware and can make quick changes, test them and smack myself with a brick. I take the original CD Microsoft for WinPE sent me and create a folder called win2k3 with WinISO and drop the files from my original unattended into it (with WinISO). The directory structure in the ISO looks like this from the root. DOCS I398 \WinPE Files like system32 etc. WIN2K3 \$OEM$ \$1 \Oracle92010 \Oracle92070 \OraclePatches \App \AdobeAcro \I386 \Usual OS stuff WinPE (pardon the layout) My Startnet looks like this ===STARTNET.CMD=== regsvr32 /s netcfgx.dll factory -minint netcfg -v -winpe net start dhcp net start nla a:\floppy.cmd cls diskpart /s CDISKPARTSCRIPT.txt REM REM FORMAT c: /fs:ntfs /q /V:OS /y REM REM mkdir c:\win2k3 REM REM \Win2k3\i386\winnt32.exe /syspart:c /tempdrive:c /unattend:\Win2k3\i386\winnt.sif REM \win2k3\i386\winnt32.exe /s:\Win2k3\i386\ /copydir:\win2k3\i386 /unattend:\Win2k3\i386\winnt.sif \win2k3\i386\winnt32.exe /copydir:\win2k3\i386 /unattend:\Win2k3\i386\winnt.sif exit ====== ===CDISKPARTSCRIPT.txt=== list disk select disk 0 create partition primary assign letter c exit ====== ===WINNT.SIF=== [Data] Autopartition = 1 MsDosInitiated = 0 UnattendedInstall = Yes [unattended] UnattendMode = FullUnattended UnattendSwitch = Yes OemPreinstall = Yes OemSkipEula = Yes Repartition = Yes WaitForReboot = No NoWaitAfterTextMode = 1 NoWaitAfterGUIMode = 1 WaitForReboot = No TargetPath = WINDOWS DriverSigningPolicy = Ignore NonDriverSigningPolicy = Ignore [GuiUnattended] AdminPassword=Password AutoLogon=Yes AutoLogonCount=3 EncryptedAdminPassword = No OEMSkipRegional = 1 TimeZone=35 OemSkipWelcome = 1 ServerWelcome = No [Display] BitsPerPel=16 XResolution=800 YResolution=600 [shell] DefaultThemesOff = Yes DefaultStartPanelOff = Yes [LicenseFilePrintData] AutoMode = PerSeat [components] iis_asp = On iis_common = On iis_inetmgr = On iis_internetdataconnector = Off iis_serversideincludes = Off iis_webadmin = On iis_webdav = Off iis_www = On [internetServer] PathWWWRoot = C:\Inetpub\Wwwroot [userData] ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx ComputerName=* FullName = "Da Place" OrgName = "Superfly" [Networking] InstallDefaultComponents = Yes [identification] JoinWorkgroup = Workgroup [TapiLocation] CountryCode=107 [RegionalSettings] LanguageGroup=1 SystemLocale=00000409 UserLocale=00000409 InputLocale=0409:00000409 [TerminalServices] AllowConnections = 1 LicensingMode = PerUser PermissionsSetting = 1 [NetOptionalComponents] SNMP=1 ======

Okay, I've figured out that if you put [GuiUnattended] ServerWelcome = No it turns off the COnfigure your server nonsense. Still looking for something to turn off ICS/ICF. The XP method of hacking up the registry seems to work but I don't entirely trust it. Still looking to see if there is a method I can set in the WINNT.sif.

Win2k3 w/SP1 + current patches slipstreamed + configuration + apps + app configuration. Trying to figure out where I can disable those two "windows Server post security Server updates" and the Manage your computer" popups in my unattended install. I can't seem to find a registry key, nor anything in the start up folder.