Over the Friday 28th and weekend of 29th, 30th and 31st May I have the pleasure of moving into some new offices and going from good old ISDN to Broadband (wish I could move my house here too but I guess it will have to stick with the ISDN). Part of the move of my business from my home to an office is moving the computers and also running an upgrade from:
Win 2k Server to Win 2k3 Server
Exchange 2k Server to Exchange 2k3 Server
Setting up OWA (I guess this is OK to run on the same server?)
Setting up a sharepoint server (hmm, do I need a new server for this?)
And anything else that looks interesting
The priorities are the Win2k3 and Exchange upgrades, the rest is frills to play with.
As I know enough about Win2k3 and Exchange2k3 to fill at least one side of a postage stamp I am on the lookout for some assistance from one more knowledgeable than me. I have asked tugs already, but he comes under the employment category of InShortSupply™ and his boss is likely to fly him somewhere else in the world that weekend, so as an alternative plan I am looking for someone else who is server set-up and wordly-wise to come and assist me.
All I can offer is some beer (no Sheepy, you really *do* need to know things about servers to qualify), some food and my thanks.
If you are anywhere near the sprawling metroplis of narrowband Milton Keynes and fancy offering a helping hand then please send me a PM. All offers (not *that* kind of offer Benny) are gratefully appreciated :thumbsup:
TL.
Useful link on upgrading.
http://www.pcquest.com/content/search/show...asp?artid=51232 (http://www.pcquest.com/content/search/showarticle.asp?artid=51232)
Cheers GFK, I'll go have a read. I may not understand it it, but I *will* read it :D
TL.
I think its a must do as it will migrate your users etc to the new active directory structure.
Err having read it I have to report back that I actually understood it and could follow it. :blink:
Is this something I should leave until the Saturday or do on the previous day?
One thing I didn't mention is that it is running as a P2P netowrk rather than a proper domain, would that change anything?
Is there a similarly easy guide to upgrading Exchange2k to Exchange2k3?
/me goes to google to find answers....
TL.
Sorry TL but I simply don't have the level of expertise you require although I am at the end of a phone if required.
At the risk of volunteering by proxy, Gandy may be the man you need.
Cheers Oldie. GFK has kindly offered to come and help on the Saturday so I just want to make sure I am prepared! From everything I hear the 2k3 upgrade path is fairly good so long as you do thingsa in the right order. From what I can work out that means do the AD & User prep first (as per the article GFK linked to above), then upgrade the OS and then upgrade Exchange. The rest is frilsl apart from installing and making work the new broadband router (the office was previously on my ISDN lines).
Are there any patches I should have to hand for immediate install when first connecting to the net for w2k3 server? /me holds USB pen drive at the ready...
TL.
Make sure this patch is on before connecting to network:
http://www.microsoft.com/technet/security/...n/MS03-039.mspx (http://www.microsoft.com/technet/security/bulletin/MS03-039.mspx)
Then 'Windows Update' asap. :)
nope not me i know a little from 2000 but nothing from 2003 :(
Does it not do an update as part of the install? i seem to remember it doing that.
Does not Exchange 2003 need a DC and active directory to even install?
I'm assuming the AD/DC is part of the migration/upgrade from the current Win 2k Server install, and that the D:\i386>ADPREP /forestPrep and D:\i386>ADPREP /DomainPrep work beforehand preps the necessary files for the 2k3 upgrade to grab them and use them?
TL.
Out of curiousity, you mention that it is not a proper domain. I take it you are running Exchange on a server that is acting as the lead AD and DC for itself? If so, how is that working out for you?
I ask as my current work domain is using an AD connector to the DC and quite frankly there have been a few issues recently with the DC's stability that are effecting the Exchange server. I've been considering correcting the DC, but also moving Exchange to be dependent only on itself in its own domain.
Unless I missed the intent of the Exchange/OWA same server question: we run both on the same (2.6GB P4/1GB) and it runs smooth.
Seems to work just fine running everything on the one box. We are using an XP2400+ with 2GB RAM with onboard hardware RAID1. We are a small business so it only needs to run 3 user accounts (although this will soon be 5). It also runs F@H 24/7 :)
We do have some issues with store.exe (as it seems a whole bunch of people do). This has been an intermittent problem where it suddenly grabs up to 100% of the CPU and almost all of the RAM, hence everything else grinds to a halt. Still not found a fix for it but from my research I'm not the only one suffering with this particular problem. It can not happten for weeks and ten happen twice in a day :(
Since we upgraded the workstations to Outlook 2003 for the functionaility we have also had the 'known issue' of the pop-up window advising you that 'Outlook is trying to retrieve data from the Microsoft Exchange Server FORTITUDE-AD', but nothing is retrieved and Outlook at the client end just seems to lock up. The only way to resolve this problem I have found is to reboot the server. Again, this is very intermittent - it happened twice last Monday, but not otherwise in the past 3 weeks. :rolleyes:
I have some spare boxes available so if it is advisable I could always run AD/DC from another box if needed.
TL.
QuoteOriginally posted by OldBloke@May 15 2004, 03:20 PM
Make sure this patch is on before connecting to network:
http://www.microsoft.com/technet/security/...n/MS03-039.mspx (http://www.microsoft.com/technet/security/bulletin/MS03-039.mspx)
Then 'Windows Update' asap. :)
ok, if you are going to use windows update, make sure to shut down all exchange services, SQL services (If running) and any IIS services. Otherwise bad things can happen.
However, I'd seriously look at getting hfnetchk pro, which is free for upto 10 machines. www.shavlik.com (http://www.shavlik.com)
I use it at work, and patching our 35 machines becomes a doddle :)
I've not actually done a 2k to 2k3 migrate yet, this is something I'll be doing in a few months, however I have a good idea on the relevant steps to take. But it sounds like you've got it covered with GFK, but I'm on the end of the phone if you need any more advice.
QuoteOriginally posted by Gandalf-LordOfJelly@May 16 2004, 02:31 PM
However, I'd seriously look at getting hfnetchk pro, which is free for upto 10 machines. www.shavlik.com (http://www.shavlik.com)
I tried to download that 4 times. Each time it told me the file was corrupted. I emailed the support people and never even had a reply :rolleyes: I like the sound of what it does, but if it doesn't work......
And thanx for the support offer G, I'll have your phone number with me :)
TL.
ok, so you've got the serial number? I'll get the latest version from work and stick it on my webserver for you to download tomorrow.
QuoteOriginally posted by Gandalf-LordOfJelly@May 16 2004, 03:38 PM
ok, so you've got the serial number? I'll get the latest version from work and stick it on my webserver for you to download tomorrow.
Cheers.
TL.
HFNetChkPro Install Here (http://storms-uk.com/uploadedfiles/hf4install.exe)
Cheers G. I checked the file I had already and it installed fine on my XP Pro PC - so the downloaded file is fine. It doesn't like my Win2K Server though :( I'm currently checking to see of all the pre-requisite software is installed, I am sure it is though......
TL.
QuoteOriginally posted by Gandalf-LordOfJelly@May 16 2004, 01:31 PM
However, I'd seriously look at getting hfnetchk pro, which is free for upto 10 machines. www.shavlik.com (http://www.shavlik.com)
I use it at work, and patching our 35 machines becomes a doddle :)
That is a beautiful thing.
I've tested and will be implementing a SUS server soon here.
http://www.susserver.com/ (http://www.susserver.com/)
Basically, it creates a local Windows Update server on your network. It checks for critical updates at designated times and downloads the patches. Then the clients all point to it and make their update calls on the LAN (much faster).
In testing, it was pretty effective and as long as the clients were configured to contact the server at boot up and check for updates, it was fast and effective.
I downloaded all the patches I thought I needed for Shavlik and made sure they were installed, still no joy. I hope the upgrade to 2003 will ensure it works! The susserver is an alternative for Shavlik? or does it run alongside with shavlik pointing at the susserver? I can certainly arrange for an extra machine to be on the network to run the susserver for me if it is needed.
My machines stay on 24/7 - they have to Fold you know! - I assume you can schedule the updates to download across the network.
Purchasing the adsl router today. Current consideration are the Draytek 2600VGi and the Cisco 836/7 type. Anyone got any quick comments before I press the 'purchase' button some time mid-afternoon today?
TL.
Well, I've just got a Cisco adsl router and it's great.
But it is pricey. Personally I'd steer clear of Draytec stuff as I've had their equipment in the past and it's been shite. Oh, and that rules out d-link too, as I think their routers use the same firmware.
QuoteOriginally posted by TeaLeaf@May 20 2004, 07:01 AM
I downloaded all the patches I thought I needed for Shavlik and made sure they were installed, still no joy. I hope the upgrade to 2003 will ensure it works! The susserver is an alternative for Shavlik? or does it run alongside with shavlik pointing at the susserver? I can certainly arrange for an extra machine to be on the network to run the susserver for me if it is needed.
Shavlik is new for me and I am exploring it now. So far I see a great tool for a domain wide update push, especially for making sure computers are patched.
SUS simply maintains a local copy of the Windows Critical Update server, self updating by preset intervals. You would need to set your clients up to point at the SUS server (a rather lengthy install guide is linked on the site) and to do something akin to: Download all updates and install/Do Not Reboot/Request Reboot from user. On a case by case basis, you can alter it to have the machines self reboot on completion (I noticed that Shevlik appears to trip the reboot by default), there are a few different options.
I like it because it means if you have 10 PC's and a 200MB Service Pack comes out, you aren't downloading 2GB to cover your machines. The SUS server grabs the one download and the other machines get it from that one.
Shavlik appears to be an active tool and SUS is fundamentally a passive one.
We're going to install SUS permanently after we redo the domain controller and exchange.
QuoteOriginally posted by TeaLeaf@May 14 2004, 06:10 AM
Over the Friday 28th and weekend of 29th, 30th and 31st May I have the pleasure of moving
Good luck TL.
We made the decision this week to start a second domain and raise it from the ground up properly. I'm adding SP3 to Exchange right now (love VPN sometimes) from the comfort of my comfy chair :)
Mid way through the upgrade and the server says 'you need this patch'. We have no internet connection and have to drive to an internet cafe to download the file. Either that or it's a 5 and a half hour download on my home ISDN :blink: or a drive to Watford to find a relative with broadband :o
Grrrr, I hate Microsloath.
TL & GFK.
Well we got there in the end. Win2k3 wouldn't recognise the onboard NIC so we had to drive to TL's place and dnld the drivers for that. Once that was done everything went ok. we had connectivity and all the pcs can talk to the server and vica versa. So a result I think.
QuoteOriginally posted by Gh0st Face Killah@May 30 2004, 03:39 AM
Once that was done everything went ok. we had connectivity and all the pcs can talk to the server and vica versa. So a result I think.
This is a a new use of "everything went ok" of which I was previously unaware ;)
Seriously, I owe you a huge debt of gratitude GFK - I would not have got through it without your hlep, cheers Jon :thumbsup: It's a testament to the friendships you build within this community that someone was willing to drive from Bristol to Milton Keynes and blow a whole day helping another member with their IT problems!
Why an onboard NIC that works fine before the upgrade should not be recognized post upgrade is totally beyond me. It's a major brand NIC (broadcom) on a major brand mobo (Asus) and W2k3 Server failed to see it after the upgrade despite giving us a clean bill of health re compatible hardware in the pre-install hardware check.
For those interested, the Microsloath installation notes state that the upgrade from W2k SBS to W2k3 SBS should take two and a half hours. I arrived at 9.30am Saturday morning, Jon arrived shortly afterwards. We both left at 11.49pm Saturday evening with still a few security patches to load (I'll do that this morning).
Next week's episode will have detailed information on how to inflict major pain on anyone to do with Microsoft, and we have a special feature involving Bill Gates, razors and tabasco sauce. Until next time, this is TL (& GFK) signing out.......
T"Thanks GFK"L.
Played GFK!
Glad you're sorted TL
PS I wouldn't drive to Milton Keynes for anything! ;)
Congrats, glad to hear it is a done deal.
When my wife asks how long I'll be away installing something, I usually just give her 'all day..and maybe tomorrow', where MS is concerned, you never can tell.
Amazing on the Win2K3 not having the drivers, I had the same thoughts you posted concerning the specs being fairly norm in the industry.
Also, cheers to GFK, having someone willing to do that is priceless. I've done it and have had it reciprocated, the feeling is great either way.
My pleasure. After all i'd only have been sat in front of the screen at home!!! But seriously I'm glad to have been of help. And leaving at that time meant the roads were lovely and clear so the journey home was a breeze apart from the speed camera I failed to spot (ooops). In fact got back in time to kill some FoCA's!!
The joys of network problems continue as some of the connectivity aspects are not as they should be:
All of the computers (MPW, PDH, CJB & FORTITUDE-AD) can ping each other.
All are in the 4TITUDE workgroup.
All computers happily sychronise with Exchange Server on FORTITUDE-AD.
CJB & PDH only show FORTITUDE-AD in the workgroup under the 4TITUDE network.
MPW occassionally showed all computers in 4TITUDE but now only shows FORTITUDE-AD.
Any idea how to get all computers showing?
All computers have access to some mapped network drives to share data.
Software which needs to install from either PDH/MPW or CJB to a mapped network drive on the server says there are network problems and that it cannot proceed with the install.
MPW has a printer attached via USB which is shared.
CJB & PDH can occassionally 'add printer' and successfully browse to it and select it, but it does not always show up in the choice of network printers.
CJB & PDH can add the printer by typing in the machine and printer name, eg \\MPW\HP3200 Laserjet which then shows on the local machine as \\MPW\HP3200 Laserjet on MPW. But this printer cannot be printed to despite successfully being added to both CJB and PDH.
It's almost like a firewall or something is stopping connection, but none of the local area connections are firewalled.
Anybody got any clues as to what to try next?
TL.
QuoteOriginally posted by TeaLeaf@Jun 2 2004, 06:55 AM
4TITUDE workgroup
All is peer2peer networking correct?
If so then: MPW, PDH, CJB are basically PC's on a network and FORTITUDE-AD is both an Exchange Server & PDC (but only a PDC onto itself in order to run Exchange)?
My gut instinct comes off and thinks that you aren't getting name resolution on your network but the connectivity is there (i.e. you can ping, but not everyone shows up in the workgroup folder).
Two things then come to mind, the easy way and the little more involved but learn something new way.
Easy: Edit the lmhost and host files on each PC to say that IP=Machine name (see file notes on format: c\winnt\system32\drivers\etc IIRC)
LMIBLSNW: activate and run a WINS server on FORTITUDE-AD and have all of the workgroup PC's use it as their primary WINS server.
Also, you *could* try to use FORTITUDE-AD as their DNS server, of which you will have to create an internal fwd and reverse look up zone for your...wait, that might now work as they aren't in a domain.. scratch that.
Pre-coffee suggestions. I have a 30 min drive to work soon, will rest it on the back burner...
Running WINS on the PDC and then specifying the WINS server in your DHCP scope would be quick and easy.
Thanks for the help peeps, problem solved.
It turned out to be a combination of things that borked the IP of the local machine hosting the printer and also the Windows firewall intermittently turning itself on without being asked. :angry:
All is well in the land of my LAN, for the time being anyway......... :P
TL.