SBS 2003 to sbs 2008 migration does not give me migration mode
Can somone please help! Ihave wasted so many hoiurs just trying to get the migriation started!
I have prepared the scource sbs2003 server and created an answer file for the migration as directed. I have this on a USB pen drive which I know works because I use the same device to load the RAID drivers on initial installation. I have installed SBS 2008 numerous times, which as you may know takes a long time. I have made the pen drive available when the server boots after installation, but every time we get the same request for information about the company name and domain name etc. When we put the domain name in manually, it says that this already exists, so I presume it can see the scource server, and is not giving me the migration mode that I need.
What can I do? I would suggest that the idea of accessing an answer file without confirmation it has been seen, wastes an awful lot of time, as you go through the complete installation only to find it has not been detected.
I currently have an installation that is asking me for all of the company info and domain name info. How can I get out of this situation, ie what can I do to ensure the answerfile is discovered abd implimented so that I can get the migration mode working.
Can I force the system to use this file from the stage I am at now, or am I faced with another full install.
Any help would be appreciated, as I have been working on this now for many hours, and cany get to first base. The fact that all of the microsoft documantation states that it confirms that the migration answer file has been located, is clearly wrong only added to my frustration.
Help! Please...
I have prepared the scource sbs2003 server and created an answer file for the migration as directed. I have this on a USB pen drive which I know works because I use the same device to load the RAID drivers on initial installation. I have installed SBS 2008 numerous times, which as you may know takes a long time. I have made the pen drive available when the server boots after installation, but every time we get the same request for information about the company name and domain name etc. When we put the domain name in manually, it says that this already exists, so I presume it can see the scource server, and is not giving me the migration mode that I need.
What can I do? I would suggest that the idea of accessing an answer file without confirmation it has been seen, wastes an awful lot of time, as you go through the complete installation only to find it has not been detected.
I currently have an installation that is asking me for all of the company info and domain name info. How can I get out of this situation, ie what can I do to ensure the answerfile is discovered abd implimented so that I can get the migration mode working.
Can I force the system to use this file from the stage I am at now, or am I faced with another full install.
Any help would be appreciated, as I have been working on this now for many hours, and cany get to first base. The fact that all of the microsoft documantation states that it confirms that the migration answer file has been located, is clearly wrong only added to my frustration.
Help! Please...
A few things here.
1. You do not have to redo the whole install every time as long as you do not press NEXT on the welcome screen. If it does not pickup the answer file, just press CANCEL and the server will shutdown and you can doot again. If you press NEXT then you have to go back to the start.
2. make sure the XML file is in the root of the USB drive (I know this sounds silly but worthwhile pointing out)
3. try using an older 512MB or similar usb drive. This solved the issue for me once
4. The SBS setup searches the root of EVERY disk on the sevrer for the answer file. Try putting the answer file on a CDROM or USB FDD
4. Try pressing SHIFT+F10 when you get the welcome screen to bring up a command prompt, copy the answer file to the root of C: then cancel the welcome screen so the server shuts down. Boot up again, see if it detects
Andy
1. You do not have to redo the whole install every time as long as you do not press NEXT on the welcome screen. If it does not pickup the answer file, just press CANCEL and the server will shutdown and you can doot again. If you press NEXT then you have to go back to the start.
2. make sure the XML file is in the root of the USB drive (I know this sounds silly but worthwhile pointing out)
3. try using an older 512MB or similar usb drive. This solved the issue for me once
4. The SBS setup searches the root of EVERY disk on the sevrer for the answer file. Try putting the answer file on a CDROM or USB FDD
4. Try pressing SHIFT+F10 when you get the welcome screen to bring up a command prompt, copy the answer file to the root of C: then cancel the welcome screen so the server shuts down. Boot up again, see if it detects
Andy
ASKER
To a non expert, this whole process is particulalry non specific, letting the OS detect or not detect an answer file without any confirmation or ability to point to its location. It just amaazes me just how random this seems to be!
I know that the pen drive works and is recognised by the server, as I loaded the raid drivers from it, so theoretically, it should be OK. I will try the shift - f10 suggestion to see if that works. I have already tried a different pen drive, but no difference.
Could I trouble you just to expand a little at which point I should know whether the file has been detected or not? As soon as the os has been installed the server re starts and asks for me to confirm the language and keyboard, I then click next, I am then given the opportunity to click Install Now. Is it at this stage that the pen drive should be inserted, and is it at this point that I should try the shift-f10?
There seems to be so little information about exectly when the pen drive with the answer file should be inserted, and so much incorrect information around. Does the answer file have to be called anything in particular? I just accepted the default name which was SBSAnswerFile.xml. Is that OK?
If you could help a little more, I would be much obliged.
Many thanks.
Nigel.
I know that the pen drive works and is recognised by the server, as I loaded the raid drivers from it, so theoretically, it should be OK. I will try the shift - f10 suggestion to see if that works. I have already tried a different pen drive, but no difference.
Could I trouble you just to expand a little at which point I should know whether the file has been detected or not? As soon as the os has been installed the server re starts and asks for me to confirm the language and keyboard, I then click next, I am then given the opportunity to click Install Now. Is it at this stage that the pen drive should be inserted, and is it at this point that I should try the shift-f10?
There seems to be so little information about exectly when the pen drive with the answer file should be inserted, and so much incorrect information around. Does the answer file have to be called anything in particular? I just accepted the default name which was SBSAnswerFile.xml. Is that OK?
If you could help a little more, I would be much obliged.
Many thanks.
Nigel.
After the third reboot this is the screen you will see if the answer file is detected.
If the answer file is not detected you will get a screen saying something like "welcome to SBS" I'll see if I can find a screenshot for you. If you get the welcome screen click cancel. If you get the welcome screen this is where you should try SHIFT+F10.
MigrationDetected.jpg
If the answer file is not detected you will get a screen saying something like "welcome to SBS" I'll see if I can find a screenshot for you. If you get the welcome screen click cancel. If you get the welcome screen this is where you should try SHIFT+F10.
MigrationDetected.jpg
ASKER
Thanks for that. Just exactly when should I insert the pen drive with the answerfile installed.
Thanks.
Thanks.
ASKER
One other thing worth mentioning, I am using the smartstart dvd which is supplied with the Proliant server. It too askes for som information like server name etc. The SBS 2008 OS is also provided by HP, and I am just wondering wether this is interfering with anything here? Mind you, I have also tried an install just straight from the SBS2008 DVD and it did not make any difference.!
Very frustrating.
Very frustrating.
The USB key needs to be inserted from a power off prior to the third (I think third) reboot. But if you have it ready it can sit in the server the entire time from when you start the install.
Do not use the Smart Start as that also creates an answer file. HP puts this on the C Drive and it may/will be detected before the migration answer file.
Load from the SBS CDROM only
Load ONE (and one only) NIC driver when prompted.
Most of the HP controllers are detected by SBS2008, so you should not need to load a driver for this, but if you do - no sweat, load it.
do not load any other drivers
Do not use the Smart Start as that also creates an answer file. HP puts this on the C Drive and it may/will be detected before the migration answer file.
Load from the SBS CDROM only
Load ONE (and one only) NIC driver when prompted.
Most of the HP controllers are detected by SBS2008, so you should not need to load a driver for this, but if you do - no sweat, load it.
do not load any other drivers
Found an image of the screen that indicates the answer file cannot be detected
http://blogs.microsoft.nl/blogs/tonykrijnen/WindowsLiveWriter/InstallingWindowsSBS2008RC0onHyperV_1923/16-SBS1st_2.jpg
DO NOT click next on this - click CANCEL
Andy
http://blogs.microsoft.nl/blogs/tonykrijnen/WindowsLiveWriter/InstallingWindowsSBS2008RC0onHyperV_1923/16-SBS1st_2.jpg
DO NOT click next on this - click CANCEL
Andy
oops - did not link
16-SBS1st-2.jpg
16-SBS1st-2.jpg
now that we have cleared that up
2. make sure the XML file is in the root of the USB drive (I know this sounds silly but worthwhile pointing out)
3. try using an older 512MB or similar usb drive. This solved the issue for me once
4. The SBS setup searches the root of EVERY disk on the sevrer for the answer file. Try putting the answer file on a CDROM or USB FDD
4. Try pressing SHIFT+F10 when you get the welcome screen to bring up a command prompt, copy the answer file to the root of C: then cancel the welcome screen so the server shuts down. Boot up again, see if it detects
2. make sure the XML file is in the root of the USB drive (I know this sounds silly but worthwhile pointing out)
3. try using an older 512MB or similar usb drive. This solved the issue for me once
4. The SBS setup searches the root of EVERY disk on the sevrer for the answer file. Try putting the answer file on a CDROM or USB FDD
4. Try pressing SHIFT+F10 when you get the welcome screen to bring up a command prompt, copy the answer file to the root of C: then cancel the welcome screen so the server shuts down. Boot up again, see if it detects
ASKER
I also have one other problem here, and it has affected me with other HP Proliant ML310G5p servers, is that whenever we have any USB devices installed on the server, it will always try to boot from it! I have trawled the BIOS, and even spoke to HP about this, to no avail.
I can re order the boot devices makeing the USB the last option, but it makes no difference. Usually, I have a workaround which I let the server start to the point where it is booting from the system drive, and then install the USB device thereafter.
Is the fact that the usb pen drive is not in from power on going to be a problem?
I can re order the boot devices makeing the USB the last option, but it makes no difference. Usually, I have a workaround which I let the server start to the point where it is booting from the system drive, and then install the USB device thereafter.
Is the fact that the usb pen drive is not in from power on going to be a problem?
ASKER
I have managed to copy the sbsanswerfile.xml file to the root of our c drive, and am just waiting for the server to complete a fresh installation again. Will let you know how I get on.
> Is the fact that the usb pen drive is not in from power on going to be a problem?
Could be, but now you know the screenshot not to go past, you can afford some trial and error without having to go through the whole install again.
Try the SHIFT+F10 trick. You can do this much earlier in the installation process if you want to. Will give you something to do in the hour or so while it is copying files and configuring..... if you are really board you can fire off event viewer (eventvwr.msc) from the command line and watch it install each component!
- got to hit the sack now. good luck.
Andy
Could be, but now you know the screenshot not to go past, you can afford some trial and error without having to go through the whole install again.
Try the SHIFT+F10 trick. You can do this much earlier in the installation process if you want to. Will give you something to do in the hour or so while it is copying files and configuring..... if you are really board you can fire off event viewer (eventvwr.msc) from the command line and watch it install each component!
- got to hit the sack now. good luck.
Andy
ASKER
I have just done a complete fresh install, but it will not now boot. I keep getting the start windows normally, or safe mode etc options and it just keeps re booting. Is there a way to recover this without doing another re isntall yet again?
you did copy it to the root of the drive *after* the re-install formatted it didn't you?
Just checking...
Just checking...
Are you getting a BSOB? if so run the HP Firmware pack DVD 9.1
where did the install get to before it went into this reboot loop?
ASKER
Yes, it was in the root of drive c: but I seem to feel the raid drivers are missing. Unfortunately SBS does not auto discover these, and whilst I did provide the drivers, and the install completed ok, on re boot I do not think they have been implemented for some reason.
I have had this before with these servers and I have not yet identified why this happens!
Thanks for your help, I will persever.
I have had this before with these servers and I have not yet identified why this happens!
Thanks for your help, I will persever.
You could try this -
Start the build off the HP Smart start, that will get all the drivers in place
The use Shift+F10 to put the migration answer file in the root of C: thus overwriting the HP one.....
Start the build off the HP Smart start, that will get all the drivers in place
The use Shift+F10 to put the migration answer file in the root of C: thus overwriting the HP one.....
good night - good luck
I think you have all the tools and info to get there now.
Andy
I think you have all the tools and info to get there now.
Andy
ASKER
I have copied an answerfile accross to the route of the system volume, but it is still not detected. Is the name crucial, or can it be called anything with an xml extension? I renamed the file from the default, so wondered if this was relevant?
If not, the question remains, just what do I have to do to get migration mode active?
I have to so say this is one of the poorest methods I have ever used!
If not, the question remains, just what do I have to do to get migration mode active?
I have to so say this is one of the poorest methods I have ever used!
ASKER
Don't worry, I have answered that for myself! I renamed it to sbsanswerfile.xml and it worked. You think that there would have been some detail of this fact in the very length migration document!
Many thanks.
Many thanks.
Are you kidding? All this time it was not called sbsanswerfile.XML?
I guess I should have confirmed this.
I guess I should have confirmed this.
ASKER
Well no actually, it was called that originally, but for the last occasion I decided to rename it so that I could identify exactly which file I was using. What I found was several .xml files in the route of the c: drive, which I would never have found without your shift-f10 suggestion. So I cleared these off, and then coppied a file accross - but renamed it - doh! Fortunately, as you had given me the screens to watch out for, I did not have to re install - again!
I know it offers the default name when creating an answerfile, but you would have thought with all the information that the migration document contains, I would have expected that this rather crucial information would be included also!
Anyway, many thanks for all of your help. A fresh start today, who knows we may have a migrated server by the end of today. Fingers crossed.
I know it offers the default name when creating an answerfile, but you would have thought with all the information that the migration document contains, I would have expected that this rather crucial information would be included also!
Anyway, many thanks for all of your help. A fresh start today, who knows we may have a migrated server by the end of today. Fingers crossed.
ASKER
The process seems to have started, but the progress bar has gone about 3cm along, and has been there for 1/2 hour or so. I keep getting a message that states the replication of AD is taking longer than expected, do I want to wait. I keep saying yes.
I know the source server is slow and old, and looking at the disk activity (queue length) is sat at 100% on the source, disk activity not as busy on the destination, but is this normal. How long should I realistically wait before I consider we have another problem?
Any advice here?
Many thanks.
I know the source server is slow and old, and looking at the disk activity (queue length) is sat at 100% on the source, disk activity not as busy on the destination, but is this normal. How long should I realistically wait before I consider we have another problem?
Any advice here?
Many thanks.
ASKER
sorry to be a pain, but the progress bar has still not moved, and we are still getting the warning mentioned earlier. This has been in the same situation for around an hour or so now. Should we restart the servers? Will the migration process re start? Would that help?
Just sat watching the disk activity on the new server, and it is on a 10kb / sec scale and peaking every second or so. The network activity is on a 56Kbs scale and has blips every second or so and peaks every 3 / seconds.
The network activity on the source server shows 0.
Is there any way we can check what is actually happening, ie whether the migration is taking place, as the static progress bar fills me with dread!
Any assistance and advice would be greatly appreciated, as I just don't know what to expect, and staring at the same screen is driving me crazy!
Many thanks.
Just sat watching the disk activity on the new server, and it is on a 10kb / sec scale and peaking every second or so. The network activity is on a 56Kbs scale and has blips every second or so and peaks every 3 / seconds.
The network activity on the source server shows 0.
Is there any way we can check what is actually happening, ie whether the migration is taking place, as the static progress bar fills me with dread!
Any assistance and advice would be greatly appreciated, as I just don't know what to expect, and staring at the same screen is driving me crazy!
Many thanks.
Shift+f10 and check event viewer
ASKER
Have checked the event viewer on the SBS2008 server, but there is nothing that keeps repeating, just one event in the application log that states :-
Notification of policy change from LSA/SAM has been retried and failed. Error 4312 to save Policy change in the default GPO's
This is only a single entry from first thing this morning, and I do not know if it is even relevant?
The only other thing I can see is on the sbs2003 server and this error has been repeated several times, but the last instance of it was last night!
It states :- The file replication servcice has detected That the replica set "DOMAIN SYSTEM VOLUME [SYSVOL SHARE] is in JRNL_WRAP_ERROR.
Where do you suggest I go from here? Do you think it would be quicker to abandon the migration, and do a manual instal, as to be honest I have had a dreadful experince with this.
One other thing, I did rasie a seperate support issue relating to this, as I was unsure as to whether you were responding or not, or whether it should be detailed as a seperate incident for the points, I do not mean to cause prblems by doing this.
Notification of policy change from LSA/SAM has been retried and failed. Error 4312 to save Policy change in the default GPO's
This is only a single entry from first thing this morning, and I do not know if it is even relevant?
The only other thing I can see is on the sbs2003 server and this error has been repeated several times, but the last instance of it was last night!
It states :- The file replication servcice has detected That the replica set "DOMAIN SYSTEM VOLUME [SYSVOL SHARE] is in JRNL_WRAP_ERROR.
Where do you suggest I go from here? Do you think it would be quicker to abandon the migration, and do a manual instal, as to be honest I have had a dreadful experince with this.
One other thing, I did rasie a seperate support issue relating to this, as I was unsure as to whether you were responding or not, or whether it should be detailed as a seperate incident for the points, I do not mean to cause prblems by doing this.
ASKER
I have just found this in the admistrator section of the sbs2008 event log :-
The file replication service is having trouble enabling replication from sbs2003 to sbs2008 for c:\windows\sysvol\domain using the dns name sbs2003.allied1.local. FRS will keep retrying.
Does this mean anything to anyone?
The file replication service is having trouble enabling replication from sbs2003 to sbs2008 for c:\windows\sysvol\domain using the dns name sbs2003.allied1.local. FRS will keep retrying.
Does this mean anything to anyone?
ASKER
Part of the above error indicates that :-
FRS cannot correctly resolve the DNS name sbs2003.allied1.local from this computer.
I can confirm that FRS is running on both servers, so how can I address the DNS resolution problem and is it relevant to my problem.
Many thanks.
FRS cannot correctly resolve the DNS name sbs2003.allied1.local from this computer.
I can confirm that FRS is running on both servers, so how can I address the DNS resolution problem and is it relevant to my problem.
Many thanks.
ASKER
I can ping the sbs2003 server by both IP address and name
NSLOOKUP however gives a server unknown error on the sbs2008, but I thought this may be because it is not fully configured. It does however identify the sbs2003 server with full name and IP address.
NSLOOKUP however gives a server unknown error on the sbs2008, but I thought this may be because it is not fully configured. It does however identify the sbs2003 server with full name and IP address.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ps. Lookup expert demazter he has written some sbs migration articles you might like to take a look at. I Am happy to walk you through it from start to end. But cannot do it tonight. My email address in my profile if you want to set something up.
Hi Nigel
Looks like you have moved on from this Q, and we solved your issues of "SBS 2003 to sbs 2008 migration does not give me migration mode"
I'll keep an eye out for the followups, but as it looks like demazter has jumped on your nex Q I will not interfere, he knows his stuff.
Looks like you have moved on from this Q, and we solved your issues of "SBS 2003 to sbs 2008 migration does not give me migration mode"
I'll keep an eye out for the followups, but as it looks like demazter has jumped on your nex Q I will not interfere, he knows his stuff.
ASKER
Many thanks for taking the time to help me resolve this issue.
ASKER
I would just like to add that I did not have to start the migration again, as once I had resolved the Journal Wrap issue, file replication started and the migration started to progress once more.
ASKER