adamt

I would recommend a RAID 5 setup with 3 disks if you want performance and fault tolerance. Mirroring won't improve the performance at all.

Rebooting a machine doesn't necessarily renew the IP. The workstation will continue to use its assigned IP address for the entire duration of the lease, provided it can ping its default gateway.

Another thing to consider with student versions of MS software, is that you can't usually upgrade them. If you have XP Student, you can't upgrade it to Vista with an upgrade edition. You have to buy the full product. Same goes for MS Office, IIRC.

It shouldn't matter that the secondary is not AD-integrated. All you're doing is telling clients to send requests to it. ipconfig /flushdns will clear out the resolver cache, and /registerdns will tell clients to send their info to a DNS server (your secondary server won't be able to register these connections itself). You need to do ipconfig /release all and /renew all in order to enforce the picking up of new settings (like DNS server addresses).

I tried this before leaving for the day but it didn't work. Did you try doing: ipconfig /release all ipconfig /renew all to force the changes to be picked up? Are you sure the workstations are DHCP clients (ie - not configured with static DNS settings)?

Is there a .MSI file you can run to initiate the setup? Can you try running from the command line to see if any error is output to the console? Anything in the application log?

If the secondary DNS is the only one which holds a record for the 'good.example.org' host, it will need to be contacted. If the primary DNS doesn't know about this host (and doesn't have a specific forwarder setup), it will do one of two things: 1) If it isn't authoritative for the zone, it will consult the root hint servers (which will fail if the zone isn't valid on the Internet). 2) If it is authoritative for the zone, it will issue an NXDOMAIN response.

Yes - you have to configure the DNS forwarder servers. Open the DNS MMC snap-in. Find the primary DNS server in the list. Right-click on it, choose properties. Open the 'forwarders' tab. Add the secondary server's IP address in the list (you can specify a particular domain for forwarding to servers if you're on 2k3). Ensure that 'disable recursion' is NOT ticked. Don't set the query timeout too low. Default is 5 seconds. If you have network issues between DNS servers, you may want to consider increasing this a little to see if it helps.

Don't know about the RADIUS side of things, but there are some issues with upgrading terminal servers to 2K3 from a licensing perspective, although not the licensing servers themselves: http://www.brianmadden.com/content/article...erver-Licensing "Does your copy of Windows XP come with a free Windows Server 2003 TS CAL? If you bought it before April 24, 2003, then it does. If you bought if after that it does not, and you’ll have to buy a Windows 2003 TS CAL." also see the comparison chart at: http://www.brianmadden.com/content/article...s-2000-and-2003

Is this an AD-integrated zone? If not - do both servers consider themselves authoritative for the zone? If so, and the primary DNS does not have a record for a host called 'good', it will authoritatively reject the request. After all, if there really were a host called 'good', it would know about it, right? ALL servers authoritative for a zone must know about ALL records in that zone. What confuses me is that you said that nslookup against both servers returns the right output. Are you sure it isn't sending back NXDOMAIN? Is this 'good' webserver in a zone which the primary DNS server doesn't know about? Does the zone exist on the Internet, and if so - which nameservers are specified as being authoritative? What kind of zone is it? (eg AD-integrated, primary, stub, etc?), and which version of Windows Server? What forwarders are defined on the primary DNS server? It should have the IP of the secondary server on there. - Also; have you disabled recursion entirely on the primary DNS server?

What do you mean by "only the primary one works?" Are you not seeing any traffic to the secondary one? Perhaps all your clients are quite happily talking to the primary and don't need to talk to the secondary? Or does it not function at all? What happens when you try to run NSLOOKUP using the secondary server?

If you have them formatted as NTFS, you can add each drive as a folder on an existing NTFS partition, using the Disk Management MMC snap-in. See: http://www.jsifaq.com/SF/Tips/Tip.aspx?id=4711

Script it! This should get you started: http://www.microsoft.com/technet/scriptcen...04/hey1122.mspx

Perhaps they're in use? Does it work when you delete them from the command prompt? If not, what's the error? How do you know they're 16-bit executables?

Here's how I did something similar a few months back: 1) Once your data is off of the old server and it's been DCpromo'd down (if necessary), rename it to something else (eg change SERVER001 to OLDSVR001) and change its IP address to something else. 2) Remove the old server from your domain, and delete the computer object from the domain. Leave time for this to replicate before continuing. 3) Disable strict name checking on the new server - see http://support.microsoft.com/kb/281308 for details of the registry key 4) On your DNS server(s), add a CNAME entry pointing SERVER001 to SERVER002, and add a WINS alias on your WINS servers if necessary. 5) If you have any IIS sites migrated across, make sure you add any required host header vaules to the new server (and add Virtual Hosts to Apache's httpd.conf file if you use Apache) 6) Add the old server's IP address to the new server's NIC - so you have two IPs on the same interface -the old one and the new one. So far, so good! You should now be able to browse to http://server001/ or \\server001\sharename, so mapped drives, printers and suchlike should all work, regardless of whether they're asking for the name or the IP address. Do yourself a favour and update people's login scripts and profile paths anyway. Much better to use the new hostname than the old one.

Seconded. Others might have different opinions, but personally I wouldn't run the 32-bit version on an AMD 64-bit chip.

Which version of Windows are you using? Which graphics card is it? Have you tried regsvr32 desk.cpl ?

Roaming profiles aren't great for ALL environments. If you have a large number of users, using large numbers of different machines, profiles can fill the space up very quickly.

I used to work for an AntiVirus company in Aylesbury, England. As a result of somebody asking us to pick him up something 'non-fattening', we decided to buy him a block of lard - which then resulted in weeks of us trying to hide this block of lard in each other's work areas. One day, this chap (who I shall call Richard, because that's his name) went out to lunch, presumably because he no longer trusted us to bring him food. We powered down his PC, and connected his monitor to another PC, running exactly the same screen saver as his own. When he came back, he tried moving the mouse to get rid of the screensaver, he tried pressing CTRL+ALT+DEL. He unplugged the keyboard and put it back in again. He pulled the power out of the back of his PC, and put it back again. Still the screensaver didn't move. Richard was a hardware engineer, so he set about taking the case off his PC, whereupon he found his hard disk had been placed with a 'lard disk'.

Well in this case, you need to find the files ntstatus.h or winerror.h Sometimes I find MSDN's a little tricky when it comes to finding header (.h) files, so I consult the .h files that come with something like WINE or SAMBA. Also - if you know the name of the file you're looking for, try a google search for the filename with the option of - intitle:"index of" You can often find what you want this way: http://www.google.com/search?q=ntstatus.h+...A%22index+of%22

Rather than go through thousands of DLLS, have you thought of opening the file with DEPENDS.exe and seeing exactly which other DLLs it is using?

If you have admin rights (try net localgroup administrators to be sure), then you should be able to change the registry key for this: HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer ... NoViewOnDrive

It depends on your environment. If you're in a networked AD environment, 2003 and XP will happily share a roaming profile. I doubt the same can be said for Vista. If (as I suspect) this is a single machine, with no AD - I think your best bet is probably a startup script which copies all your .url files from your other profiles into each other profile. Perhaps you could use ROBOCOPY /MIR to achieve this?

You can definitely move pagefile.sys (or rather - create a new one on the second partition and get rid of the first one). IIRC, on NT4, if you moved the pagefile to a partition other than the system partition, you lost the ability to create crashdump files in the event of a BSOD. Not sure if this is still the case with W2K3.

Firstly - tell them *NOT* to do this. If they don't know not to do it, they'll keep on doing it. Quote any relevant terms in your employment contracts, AUP, etc... Secondly - if you can find out who is doing/sanctioning this - speak to them directly and explain the problems. If it happens again, deprive them of their mailbox for 24 hours and cite 'data corruption due to unclean shutdown' as the reason. That should make them think twice in future.