Discussion Locked

Open the WS2K3 discussion

0 helpful
53 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Take this opportunity, network admins and support pros, to post your Windows Server 2003 questions, enter comments about our WS2K3 e-newsletter, and offer suggestions for future tips.

If you haven't subscribed to our free WS2K3 e-newsletter, you're missing out on some great information. Subscribe today!

https://www.techrepublic.com/techmails.jhtml?repID=r001

53 replies

by djent

Lets wait for the gold BETA and we will have something to talk about.

by curt geiler

Windows Server 2003 was released on April 24, 2003. I've been testing it since Beta 1 and have upgraded two servers so far.

by jlemay

anyone know if it's covered under software assurance? I have four licenses for "Windows 2000 server" covered under software assurance, but when I check at https://eopen.microsoft.com , they don't list 2003 server as the current version yet.

by spongebob_squarepants

Just curious, in production environment, have you experienced any troubles with Server 2003? We have a mixed environment with NT 4 and 2K servers, would like to upgrade to 2003, but no money to buy servers to replace the NT 4 boxes.

by hillsa

I have the 2003 Eval kit installed on a server and tried to install SQL 7.0, I was promptly informed that it was not supported by 2003. I am willing to bet that any version of Exchange before 2000 is not supported either. The best bet is to determine the use of the server and if you want/need to purchase an updated application for it. Also, watch out for the licensing snafu you could get into with any new desktops down the road.

by djent

Any OS prior to W2K cannot connect to it either. Start your upgrade spreadsheet now and don't forget the hardware. Do you see a recurring pattern here?

by hal 9000

But we are only in the trial stage and 2003 Server is more an evolution rather than revalution from 2000.

We still have quite a few NT4 boxes about but this is mainly because a specalised program won't run on the 2000 or 2003 versions and at present there are no plans to rewrite this program.

But from my impressions so far if you can use 2000 2003 will be easy there are some more security features but the main stumbling block is still IE 6 as it had a security flaw in it on release that has just susposelly been fixed but so far I haven't had the time to actually check just how good the patch works other than not having any problems in installing it.

by bichelmo

Does anyone know of a way to connect Windows 2003 and NT4 so that you can authenticate to an NT4 domain.

by hal 9000

You have to alter the default mode of 2003 into "MIXED MODE" from its native mode. Then you will b e able to work with NT4.

by amrish

You can not get NT4 authenticated by Windows 2003 Domain or Wonows 2003 domain by Windows NT4, whithout upgrading NT4 first in to Windows 2000. there are major diffencies in both Windows 2000 Diresctory and Windows 2003 Directory, so watchout for some problem.

by hal 9000

If you run Y2k3 in mixed mode it will work with NT4 and so far it does here it is just like y2k but if you allow it to load in its native format it will not comunicate with NT4. To date I haven't had a problem and we have 3 NT4 servers here that only run one program for earthworks as it won't run on anything newer and presently there are no plans to rewrite the program so for the time being we are stuck with NT4 but then again the program is only $80,000.00 Au so it probably isn't all that important like if it wasn't used then we couldn't get the earthworks to the specs that we currently do as there is laser equiptment all over the place on both the machinery and leveling sights on the work site and we can bring any work to within 2 mm. Soguess who's sticking with NT4 for the forseeable future and w2k3 is communicating with it OK.

by darkside

You can install Exchange 2000 on WK3 , as it tells you when you try to install it.
You just need to install Service Pack 3 for Exchnage upon initial install.
RTFM

by fred

I talked to Microsoft and was told that the Exchange 2k uses a different security than Server 2k3. I had to install the Exchange 2003 bata which is the Exchange 2000 for the most part. I have had no problems so far. I have not even rebooted my servers for over a month.

by psifiscout

In the true tradition at Microsoft, their newest OS is touted as being a "cure all" for something or other, in this case it's legacy support. As I have not yet fully explored this capability of Windows Server 2003 I cannot fully address this issue. However, if the legacy support has not markedly increased over that of Windows XP, the claim is false. Over the course of numerous network installs of WinXP I have had the misfortune of having to deal with legacy support issues in everything from applications to hardware (primarily older printers) and using the wizards in XP I have yet to get any of the legacy hardware/software to function. The selections are indeed included in the menus, but the resulting solutions simply failed to support the hardware/software desired by the client.

by lloyd walker

To add to the issues. If you have an older SNAP server it has problems with W2003 as well. I've made all the changes requested by SNAPappliance support and still can't connect to our SNAP server. This also appears to be server & client related. If I boot from a Windows 95 boot disk, I can connect to the SNAP server. If I boot up my XP OS it won't connect.

Any suggestions are welcome

by gordoncampbell

XP is far better than 2000 in this respect. If 2003 is even better then this is good isn't it? Its easy to whine about things not being 100%perfect but whats the point? Its better than its predecessor and that wasn't bad so just get on with using it!

by hal 9000

Not a desktop OS and as such the important items are SCSI drives, RAID ARRAY drivers, Network drivers, possibly broadband modem drivers and the like.

Because this is a Server OS what isn't important are things like video, sound, all the unnecessary plug in cards that don't have any usefull application for a Server like video capture cards and the like.

This OS is susposed to be used to host a Domain or even run a gateway or a host of things like that.

What it was never designed for was to run on a desktop where things like new video cards, sound cards, video capture cards and all those things while necessary for a user application arn't needed or for that matter supported for a Server as they are susposed to store data and make various things available across a network dpending on exactly what the server is set up to perform. After all no one would expect a dedicated ISA Server to run games would they?

If you want a desktop OS then stick to XP and leave 2003 for what it was originally intended for.

by fazeel

Most of the ISA Devices are not supported in W2K3. Modems, Sound Cards and most of the other Devices for ISA Slot. It has no builting drivers. To use these devices I gave the PATH TO INF FOLDER OF WINDOWS XP and it took the devices and when needed the files I also redirected the request to Windows XP System32\Drivers Folder.

Every thing was fit and fine no prob but a bit tricky.

Best of Luck you all.

by seyiogunwumiju

hi,
i am a nigeria residing in lagos i want to start writing my certification from the start pls can yu help to send information on the centre here and howto pay for each stage
seyi

by steven-s

This is in responce to the newslatter stating how to keep accurate time on your 2003 server.
Per article Q289689 and KB289689 from Microsoft, a Domain Controller or any XP-based computer that is a member of a domain must relay directly on the domain's NTP service. Internet time synchroization is not an option.

by neilpub

This "tip" seems to describe horrid internet manners.

To quote:
"In addition, make sure that all of your clients' time properties are
configured properly."

This article already makes the mistake of telling the readership that every server ontheir network should sync directly against a NIST time source.
The quoted section then componds this error by impling that every client should also point to a NIST source.

If the advice in this "tip" is followed, we will soon see that the various public agency reliable time-sources will be so swamped with requests that they will be as overloaded & useless as microsoft's time.microsoft.com.

Who checks these "tips"!

First off, setting through the clock is NOT the correct method, and there should only be one device per site (or maybe one per connection if you have multiple pipes to the internet) that touches a reliable time source.

Each server and client in an organization should then point to the local server at it's time source.

Additionaly in Win2000 and Win2003 you should use a list of timesources so that there is some failover.

The correct basic method of configuring your local NTP Win2000/2003 server to query an external timesource is with:
Net time /setsntp:"xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy zzz.zzz.zzz.zzz"
Where the xxx/yyy/zzz is the ip address of level 2, level 2, level 1 timesource.

More advanced time source configuration can be done by using (in Win2003) w32tm command (w32tm /? for options).

by grandphython

Hi All,

We have multi domain, complete trusts. We were all NT4 and have (for the most part) successfully upgraded 3 out of 6 servers to Win2K3.
One problem though. Browsing across domains no longer works. Curiously not on all the domains though. However, we can ping and map drives to ANY PC across ANY domain.
Example:
Domains A,B,C, and D.
A,B,C can see all domains listed and get inside to see the actual individual PCs. D can see the domains listed, but can't see the PCs inside the domains.
At first I thought WINS issue, but we can map drives and ping names no problem.
Any help, much appreciated.

by fred

I baught 2 2k3 eOpen Licenses and I Ask, and they said that If I had baught the software assurance, it would have been covered. I think you'll have to renew it every 3 years.

by fred

I have 2 production 2003 serves that have been running since may 20.

I have exchagne 2003 bata running with no problems(microsoft suggested to use it.)

I also have about 10 win98 clients logging on.

the only problems I ran into at the begining was that there was no anti virus supported, I had to mess with Norton to get it installed.

There was no Exchange anti virus so I had to resort to Nav for Gateway.

and Veritas informed me that the ver 9 was not supported.

2003 Server isnow Supported Bye Symantec and Veritas ver. 9

by burgmann.tom

15 users - 6 XPpro, 6 W2Kpro, 3 W98

SBS running on W2Ksp3 PDCserver. W2K3 DCserver added on Jun6. Veritas 9 used for backups.

One W98 & one W2K experience Excel file renaming to numbered file since we turned on DFS between the two servers. No other problems to report.

by Member 36438744

I have encountered the same problem when DFS enabled on W2K3 DC Server, 9 WinXP Pro workstations all have same problem with Excel files renaming to numbers, what I found is that it only renames after Excel is closed. Looking for a solution but nothing as yet.

by t bowman

I don't mean to be rude, but some of these folks need to get some training or at least do some reading.

Start here: http://www.microsoft.com/windowsserver2003/default.mspx

I might also suggest: Mastering Windows Server 2003 by Mark Manasi - especially if you have no experience on Windows 2000 and ADS.
I certainly encourage questions and will help all I can, but one must get a good foundation.

by administrator

Hi,

I'm going to be upgrade our PDC from NT 4.0 to win2k3 in the coming months. Can anyone provide a project plan that they might have used or advise how i wshould go about creating a project plan. Ii dont want to be left with egg on my face as Ii have never run this type of project before.

Kind Regards,
NF.

by thongthe

I think there is still a bug. Under the Located on this volume, It does not allowed me to change the disk (c: to d:). Are there any service pack?

by hal 9000

The only provided hot fix for 2003 is a small patch for IE6 and so far that's all that's been realeased for 2003. Acording to MS it susposed to be the most secure OS that they have so far released and out of the box it's susposed to run without problems or so they say.

by davidza

To change the location setting after enabling Shadow Copy of Shared Folders you will need to "disable" the target volume. Doing so will enable you to select a different storage area location. However, you will loose any shadow copies created underthe original storage location. So take caution in making these changes.

Regards,
Dave Zank
Technical Product Manager
Microsoft Windows Server 2003

by black_eyed_pea

Is there yet a strong case to migrate from Win2K3 to WS2K3? What about from MSSQL7/MSSQL2K to MSSQL2K3? Exchange 2K to Exchange 2K3? I'd like to see compelling reasons for each. I'd also like to know if the community thinks it is still necessaryto wait for SP1 to be released or if Microsoft's method of eating its own dogfood is finally paying off.

by k-n-ballantyne

I have recently deployed a new server and have had a relativley good experience for a new eeease product.

My major issue is still getting software that will run backup's under 2k3. Seagate have apparently released an upgrade version (at an addtional cost) of software but none at this stage for new installs. The rest of the install was relatively straight forward.

by tomereynolds

Compelling Reason #1

It is stable right out of the box, even pre-SP1.

I've been running W2K3 Server for over 6 weeks on my IBM laptop and it has yet to crash. I can't believe it is this stable. (Well there was one slowdown, but I caused it by loading Nortel VPN drivers for 2000.)

I have always waited (leasons learned many years ago) until after the first SP before running a MS OS in production, so I would reccommend that users wait until SP1. I am still amazed though.

If you need a new server, go for W2K3. I would be hard pressed to explain why an upgrade was nessesary from W2K. But yes, migrate all Nt4 boxes to W2K3 when the time comes.

-TomR

by ricardomenendez

I'm not a messaging or OS system expert and can still think of a quite a few upgrading reasons. But refered to DBMS SQL Server 2K is much a more solid player than 7 was. It fixes endless flaws and limitations from the previous versions. I always believe client OS upgrades are 50% technical, 50% based on GUI improvements or not-so-important-or-demanded features but as to server upgrades Windows has proven to take server upgrades really seriously. Windows 2K Server is such an enormous change regarding NT4 as W95 was from Win 3.11...Serious flaws at launching date haven't been an issue for quite a while (Exch Serv 2K3, Win XP, even SQL Serv 2K) so I guess it's worth the risk at least getting the chance to gain hands-on experience with the OS these first months.

by modox

We have just moved our infrastructure over from NT4 to Windows Server 2003 and it worked fine. You do need W2K3 in mixed mode then you set up two one-way trusts between the domains. if you want to you can then use the AD Migration Tool (ADMT) V2 which will not only migrate the users but also add the NT4 domain users to the W2K3 ACL's.

All of our major systems are now over we are only waiting for Exchange 2K3 so that we can migrate E5.5 then the NT domain will disappear forever.

by maxi2x

i have a big problem. i have two domain controller in my network i want to migrate from 2000 to 2003.i also have any exchange server running in network.i am also changing my server two server to new ones.It is the new ones i want to migrate to 2003.It is a new server with no operting system.i do not want my exchange to stop working.after migrating, i want all my 500 user to log on to the domain.i also want to replace my two domain names while migrating.i will not used the the old name.i want you to really help me with solution.

by alvaro6

Hi Maxi, This is not a big problem, you just have to document your self about how to do this, then you will see the many alternatives out of the box with these excellent pair of prodcuts(Win&Exch).
This subject is not as simple or short to give just the correct answer, there are more than one alternative when upgrading or migrating you SW or HW, but the best alternative depends more on your specific scenario.
Some questions comes now to my mind:
What is the version your production Exchange Servers?
What are the Services Packs intalled on the OS and Exchange installatoin?
When you talk about domain names, are you talking about Active Directory domain names or just SMTP domain names for your message system, you don?t really have to have to change your AD domain name to get a different SMTP domain name for your message system. if you are talking about AD domain names, another alternative to do not worry about all your well :) stablished infrastructure and final users issues and ads. (Permissions def., interoperability between domains while migration, etc)could be use the new Win 2K3 feature: domain rename, but you must have your Forest functional level switched to Win2K3 & Exchange 2003+SP1 in native mode. with this new feature you will benefit a lot because of dealing of the administrative overhead a migration between domains implies.
So i will supose you have Windows 2000+SP3 and Exchange Server 2000+SP3 installed on your prod. environment, also i supose you will upgrade your SW, and thinking about the less interruption to your service and if you already have the new HW, a way you can do this Hardware Migration in a few words:
1. Install Windows Server 2003 on your new servers promote them as Domain Controllers, but before doing this please read: http://support.microsoft.com/?kbid=325379
2. you do not mention your Exchange version, so i asume is 2000, if this is real you already know the integration with AD, but please take time the time to read the Chapter 3 from the Exchange Server 2003 Technical Reference Guide, you can download it at:
http://www.microsoft.com/downloads/details.aspx?FamilyId=3768246D-C9ED-45D8-BECE-A666143CBA4E&displaylang=en
3. Install on the new server Windows 2003, then install your new Exchange Server 2003 just as one more server in your actual organization. If you really do not want to consider this migration or upgrade decision,you have to read the appropiate content (almost everything) on this tow important guides:
a. The Planning an Exchange Server 2003 Messaging System guide will give you a clear idea, about the best path to do your migration or upgrade.
http://www.microsoft.com/downloads/details.aspx?FamilyId=9FC3260F-787C-4567-BB71-908B8F2B980D&displaylang=en
b. The Exchange Server 2003 Deployment Guide, contain all general details to make of your mig or upgr. the best plan to your scenario.
http://www.microsoft.com/downloads/details.aspx?familyid=77b6d819-c7b3-42d1-8fbb-fe6339ffa1ed&displaylang=en
c. See also this KB:
Considerations when you upgrade to Exchange Server 2003
http://support.microsoft.com/?kbid=822942

4. At work-off hours gradually move your users mailboxes to the new server.
5. At work-off hours replicate all the content of public folders on the new server, force replication inmediatly, wait for replication, be sure absolutly all of the contents had replicated to the new server, if positive eliminate replication inmediatly for the old server, be sure is working fine. in this point when i say public folders i?m talking about the manually created folders, NOT the system folders. see point 7.
6. Verify the correct function fo those two Exchange server. If positive at this time you will proceed to remove your old Exchange server.
7. Before you can safely remove your old Exchange Server you must do some aditional tasks described in this KBs:
a. XADM: How to Remove the First Exchange 2000 Server Computer from the Site
http://support.microsoft.com/default.aspx?kbid=307917
8. Now you have your new servers working with Windows 2003 and Exchange 2003, if your forest functional level is Windows 2003, and you are only working with Exchange 2K/2K3 servers, you will like to switch your Exchange mode to native, you will have some new interesting features with these levels.
9. Finally the best thing you can do before configuring any Exchange Server 2003 feature (really any server)is to read the appropiate guide, there are enough for IT Pro's at the Exchange Server 2003 Technical Documentation Library:
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/default.mspx
Also you will like this Exchange Server 2003 How-to guide:
http://support.microsoft.com/common/canned.aspx?R=d&H=Exchange%20Server%202003%20How-to%20Guide&product=exch2003&LL=kbexchangeserv2003search&Sz=kbhowto%20or%20kbhowtomaster
I hope this will help you!,
regards and have a good readable weekend :)

by jcalexandres

Hi ... I am almost in the same situation, but I already added a win 2003 to the 2000 domain, my case is that I have extra computers to do the process.

You need to run adprep in the master role server, this will prepare the domain to migration, I imagine you are using Exchange with active directory, so adprep will take care of that too, from there you will need to select a path for migration, either upgrading the actual servers or fresh setup of the 2003 OS on a new machine.

I will update you later as I work with my project.

Good luck!

by santynet

Does any one have a project plan on migrating the a domain & A.D. from a 2000 Server to a new 2003 Server (Separate Box)?

I want to make sure I don't loose the domain.
Should I add it as a secondary PDC and replicate it? Would I be able to make it the primary PDC later? Any help would be appreciated.

Thanks,

SAnty

by jcalexandres

I will like to know if anybody have run trough the dilema of adding a win 2003 DC to a win 2000-based domain ane then considering renaming the domain?

I have a win 2000 domain, the administrator before me named it win2000.com, which I didn't like since started working here, but lived with it. Now I needed to add a win 2003 server, make it a domain controller, which I have achieved, but further I need to rename the domain to a domain we have registered, then add a win 2003 machine also DC to use Exhange 2003 Enterprise.

If anybody have any experience with the process I am doing, I will appreciate to post your experiences and things to consider when renaming, since I have an enterprise of 300 machines (WAN/VPN), which can't afford to have down.

Thank you!

Jorge Alexandres
Network Administrator

by darkside

yes, the renameing function is always a bit of a pain.
All the domain controllers have to be at the 2k3 level and then you will have to alter the domain membership of all clients (unless they are XP at the right level)
Almost too much trouble but interesting to do.

by cyrusngugi

Hey Guys,
i have a problem with my w2sks server where XP client user taking longer time after entering the password, when i logging on the local machine as administrator logging is fast.
Any idea will appreciate.

cyrus

by gergerdotcom

i just finished installing my Win Server 2003 Standard Edition Service Pack 2.

i want to know what's best to do with it if i'm going to create or setup either an Active Directory (AD), or a DNS, or Domain Controller (DC)?

likewise, can i make my Win Server 2003 SE SP2 be configured with all the 3-functions such as AD-DNS-DC?

by the way, my planned is to setup a SOHO using 2-PC that has a Win XP OS, as well, 1-PC with open source OS.

hoping for a kind and helpful assistance:)

cheers!

This discussion is closed to new replies.