clutch

I know we have a how-to around here about doing this, but I saw this link at Technet today and I thought I would post it. It explains what each of the services are in Win2K, and what effect they have on the OS. Might be a good read for those who think they want to shutdown any of these services. http://www.microsoft.com/technet/treevie...cs/win2ksvc.asp

Wow, I have always thought Compaq servers kicked major a$$. While we only have 4 of them, they have all been topnotch performers. Both of the consumer lines of HP and Compaq have been lame, and I am hoping that the commercial quality of Compaq doesn't falter as well due to the merger. In particular, I would like to say "long live the ROMPAQ!"

I can't seem to find any how-tos on the subject, but there is software out there to ease the burden. You can check out NetIQ's offering at: http://www.netiq.com/solutions/windows/default.asp and see what they can do to help out. It would seem that Novell Groupwise would have some ability to export your email account info to some sort of basic format as Ryoko stated, but that may be quite cumbersome depending on the amount of accounts you are dealing with.

OK, I just got Vis Studio.NET Beta 2 from Visual Studio Magazine, and I installed it. However, while it can find my .sln files and try to open an existing solution, it tells me that I don't have any programs assigned to open .vip files. Now, should I manually assign Vis Studio.NET to open it? This seems kinda silly, and the help file has a link for migrating existing solutions, but no info is on that particular page (just a place holding header). I sent in a bug report, but I have a feeling that it's something simple. Anybody know what this is about?

Well, just so you don't think you are being left out in the cold, I am looking into this. I haven't had to do this, and I haven't messed with Novell in quite a while. The only link I have found so far on migrating to Exchange is more around developing the team to do it rather than a walk-through. If I find more info, I will post it.

Get a new job.

I have never found it to be a hog myself. And in fact, I have preferred its performance over FAT32 in speed and durability. The MFT does take up a fair amount of space (like 12% by default) though, but that's never been an issue for me either.

Well, IIS should be running under the system account, so I don't know why it would behave any differently. Also, are you using FrontPage extensions? Maybe they fizzled out and are giving you issues. I got the newest ones that support FP2002, and they seem to be working fine (and are a bit faster as well).

Set the ftp site to permit read/write in the IIS MSC, and then use NTFS permissions on the individual directories to control what the user can and cannot do.

Well, here's the link to get SP2 for Office 2000: http://office.microsoft.com/downloads/2000/SP2upd.aspx And as for integrating it, you can make an admin image of office, and then apply the update to it. This link covers those methods, and the location of the image up[censored] SP2: http://www.microsoft.com/technet/treevie...es/off2ksp2.asp If you make an image, you can then imbed the serial number and options that you want to use. At that point, you can simply run the setup from the image and get the same options all the time.

OK, while I am familiar with the situation you speak of, I have never heard of it termed as "cluster overhang". Now, as for performance, I wouldn't use large clusters on a disk that would contain many small files (like text files, for instance) because the MFT in a NTFS drive will actually store the data directly if the file is less than one cluster in length (hence my decision to only use larger clusters in cases where I store large files only). I have found 8K to be a great median for most systems, as I don't have wasted overlap (or "overhang") with a large cluster just simply not being large enough for my files, and having barely filled clusters all over the place.

I am not sure what you are talking about with respect to "cluster overhang" and whether or not it is desireable. From what I have read, you want as little free space as possible between files anyway (isn't that fragmentation?). And, I have found NTFS to be faster AND way more reliable than FAT/FAT32. Now, as for cluster size, I tend to use 4K on partitions less than 4GB, and 8K on partitions that are larger. If I plan on creating a partition to store large files (like ISOs or ZIPs of installable program images) I will go to 16K. This may be the reason why I have found NTFS to be faster, as that I tend to change cluster sizes depending on my needs.

Yeah, I haven't seen any imaging software that will work with NT/2K server. I can imagine that there isn't a high demand for it, plus servers tend to be more mission critical, and you can get the occasional image failure that could ruin your day. I think the main reason though would be trying to support all the software RAID configs in the server version of NT. I know that partition magic from powerquest will not work in NT Server, but ServerMagic (from powerquest) works just fine.

Check this out: http://news.cnet.com/news/0-1003-200-6658768.html?tag=tp_pr If you can't beat 'em, sue them again. Count on 2 things: 1. More lawsuit BS 2. MS rushing WinXP out to beat any possible injunction Both of which hurt the OS. I am pretty sure I'll be hanging back until SP1 on this critter.

Are you pinging by name or IP?

Good luck, bud.

The only name I use for them is their "given" (network) name.

No way! That's brilliant! I will now be asking both the Wisconsin DOT and Illinois DOT for refunds due to all the traffic jams I have been in. I can't believe I never thought of this before. Now, if I could get the state attorney generals on-board with this, it could really work...

That was it. I could remember "london/perth/brisbane.<something>.msft" but I just couldn't remember the "nwtraders" part.

DNS systems would be following by the domain suffix such as "home.com", and can be non-standard ones like "domain.msft" (".msft" is usually seen in lab networks for MS-based courses). So, somewhere along the line you have something other than DNS resolving the names "mail" and "news". That is rather handy though, as I usually map those names on my networks on the WINS box.

By translating, I am referring to name resolution (where ntcompatible.com equals 216.234.186.180 using DNS) such as DNS to go from a name, like "mail", to an IP address. So, I was just wondering what system would be using the NetBIOS name resolution format in your case. However, I am getting the impression that you might not know, so I was just hoping that someone who does could shed some light on this. Do you have a WINS IP entered into your IP properties? You can see this if you open a command prompt (cmd.exe), and type ipconfig /all. You would then see "Primary WINS Server". The only other methods would be broadcasting and lmhost files, neither of which I could see being particularly attractive in a large scale network like @Home.

Then something, somewhere is translating the name "mail" into an IP for you. So, while it's fine that it worked for you, I would like to know what name resolution service you are using to get it to work.

Less pop-up ads?

"Ping Mail" would assume that there is a NetBIOS resolution (such as a WINS server on a network with "mail" already assigned) for the name "mail" to an actual IP. So, if you don't have a name resolver with that entry, then executing that command will not help you. As for where to get the POP info, try going online to www.home.com and using the help link there. They will more than likely list the pop and smtp servers there that you can use. Also, try to use the friendly name (pop.home.com or whatever) as using the IP directly can cause problems later if they change servers.

If you go to the small business or corporate sales sections of these sites, you will usually see Win2K on those boxes. I get IBM ThinkPads and Dell Laptops with Win2K pretty easily.