Re: SBS 2003 - SBS 2008 migration issues

The migration documentation starts and ends with the server, theres still plenty of things to do on the workstations. No part of the steps I followed in the migration failed as such, I just got to the end of it and still had plenty of work to complete.

"Les Connor" <les.connor@xxxxxxxxxxxx> wrote in message news:e1TqCwuWJHA.3808@xxxxxxxxxxxxxxxxxxxxxxx
It's more likely a case of missed steps; not your fault though, as the migration document(s) are not easy to follow. There's a newer migration document in the SBS tech center in Technet, version 2 I believe.

The migration steps were extensively tested, but the documentation falls somewhat short. If you know the SBSMigration product, it also is essentially documentation, allthough some tools are provided. More importantly, support is provided. I'd expect the SBSMigration kit for SBS 2008 to be similar; allthough the way SBS 2008 is installed (from image) is way different than any previous version and therefore so will SBSMigration.

--
Les Connor [SBS-MVP]


____________________________
"Aart Jansen" <Aart@(nospam)xnet.co.nz> wrote in message news:FCBEA419-B5F9-400D-88A4-F3E4CD9665C2@xxxxxxxxxxxxxxxx
Well my experience with the migration has taught me a lot. And I wont be doing another one the same!

Firstly a lot of my trouble with networking (DHCP) / Applying group policy was overcome by putting in a new network switch.

But heres a list of wierd issues.
oldcompanyweb - despite being granted "full control" users are getting access denied when attempting to add to it, reassigning the rights they already have seems to fix it, not too bad I guess for my 10 user site, bugger that for a big site.

Many apps (finepix / acrobat reader 9 / Microsoft picture it... the list goes on) on workstations are extremely slow to open. A quick regedit and search for the original servers name shows vast quantities of entries (mostly redirected my docs from old server). Most apps are ok are a remove / reinstall. not all. For this reason alone I wont be doing another MS migration. Actually I find the migration a complete joke with so many workstation issues and other parts like printers / network neighborhood left to fend for themselves.

Anyone know if/when Jeff Middleton will release a Swing for SBS 2008 ? Keeping the same server name would save such a huge headache.


"Les Connor" <les.connor@xxxxxxxxxxxx> wrote in message news:uy9BAoXWJHA.200@xxxxxxxxxxxxxxxxxxxxxxx
I'm sure it's quite resilient, but one has to learn it first. Or, more specifically, learn what *not* to do.

--
Les Connor [SBS-MVP]


____________________________
"Aart Jansen" <Aart@(nospam)xnet.co.nz> wrote in message news:80A7E20A-C209-4316-9206-DFE864B6A0FC@xxxxxxxxxxxxxxxx
It's not a test network, the testing I did (due to its lack of any realworld relevance) seemed really successful.

It's defiantely the last one I do for a while. TBH I had hoped for a less 'fragile' platform SBS 2003 seemed way more resilient.


"Les Connor" <les.connor@xxxxxxxxxxxx> wrote in message news:eiXN3YWWJHA.3688@xxxxxxxxxxxxxxxxxxxxxxx
Remove hyper-v role from the SBS, and then run the fix my network wizard.

DHCP cannot work properly with the hyper-v role, and probably DNS, neither will the configuration wizards.

I sure hope this is a test network, and therefore isn't your first or last migration. Folks need to be cautioned about jumping in with both feet before learning the ropes; it could have dire consequences in a production network.

--
Les Connor [SBS-MVP]


____________________________
"Aart Jansen" <Aart@(nospam)xnet.co.nz> wrote in message news:FEB9E497-CD3E-4405-8E22-5AA3DBE3D48A@xxxxxxxxxxxxxxxx
Thanks Susan,
If I remove the hyper V, will it "unhork" the wizards ? Is it mainly because the virtual network connection confuses the wizards ?

I am having real issues with DHCP. clients losing the ability to use it after removing trend client, reseting winsock / removing network components / reinstalling teh client don't bring it back. a system restore DOES, but I need to remove the trend client as it's set to look at the wrong server anyway.

My printer issue stems from the Konica C352 Bizhub being a 64 bit driver and the cleints being 32 bit OS's. When I add the 32 bit driver to the printer it simply tells me it's not a suitable driver, and to try adding the driver from a 32 bit client. I had no problems adding the other printer on their network (an old Laserjet 4+)


"Susan Bradley" <sbradcpa@xxxxxxxxxxx> wrote in message news:%23fvfahOWJHA.1188@xxxxxxxxxxxxxxxxxxxxxxx
Aart Jansen wrote:
So it all went according to plan, so it seemed.
#1 User accounts - theres no permissions or wizard to assign to multiple users rights to RRW / OWA / PCs, user roles is blank and I can't see how to give existing (imported) users roles.
#2 Trend CSM, to be honest I've had it with this product. Removing the trend agent has stopped DHCP working on all but 2 workstations. reinstalling from the new servers client doesn't restore DHCP client function. MSA stops the exchange 2008 transport service (ie all email).
#3 Payroll app from a new share with full permission on 2008 doesn't work. times out with a lock / timeout error (paradox database based app). locally it's fine.
#4 Blackberry - lol no BES / BPS support, and theres no ETA.
#5 Printer shares - 64 bit driver exists and works, however the 32 bit driver doesn't get recognised as the same driver/device so wont install on the share, hence every workstation needs its own driver installed and coinfigured to talk to the printer directly *sigh*

A question I have is, If I install hyperV on the SBS 2008 will it run a win2k3 server (for blackberry) ?

It's not supported (and will really hork up all of your wizards big time) to install HyperV "on" the SBS box.

In the migration document you run the User wizard to push permissions to the imported users.

What are the exact permissions on that share?

Printer Shares,

You will need to add the printer in Printers under the Control Panel before you will be able to see the printer in the SBS Console, or add it manually to the console.

Remember to elevate when adding a printer by right clicking on the Add Printer icon and clicking on Run as administrator.

Once the shared printer is setup and seen in the SBS Console, the best way to automatically deploy that printer is via the Print Services Role in the Windows Server 2008 Server Console.
Click on the Print Services Role and scroll the right pane down until you see Resources and Support --> Recommended configurations, tasks, best practices, and online resources.
click on Deploy printer connections to users or computers by using Group Policy and Print Management.
Click on the More about this recommendation link under the list to bring up the Help topic.
Or, click on this link to get to it in the TechNet Library: http://technet.microsoft.com/en-us/library/cc754699.aspx

(stealing from Philip Edlers comments
http://technet.microsoft.com/en-us/library/cc546031.aspx









.

Relevant Pages

  • Re: status of mas90 client
    ... Gregg Hill wrote: ... The Dell PE 2800 server ... The workstations are slow to open applications, slow to save files to the ... SBS BPA gives a clean report. ...
    (microsoft.public.windows.server.sbs)
  • Re: status of mas90 client
    ... Gregg Hill wrote: ... The Dell PE 2800 server ... The workstations are slow to open applications, slow to save files to the ... SBS BPA gives a clean report. ...
    (microsoft.public.windows.server.sbs)
  • Help with Swing Migration
    ... from anyone who has used Jeff Middleton's Swing Migration Kit. ... includes the tools) to do a SBS 4.5 to SBS 2003 migration to new server ...
    (microsoft.public.windows.server.sbs)
  • Re: << SMB Nation - THE get together for SBSers>>
    ... > SBS MVPs expected to hang out there: ... > looks like a session on SBS Migration will be added. ... and bringing the new SBS server in almost transparently. ...
    (microsoft.public.backoffice.smallbiz)
  • Re: << SMB Nation - THE get together for SBSers>>
    ... > SBS MVPs expected to hang out there: ... > looks like a session on SBS Migration will be added. ... and bringing the new SBS server in almost transparently. ...
    (microsoft.public.backoffice.smallbiz2000)
Loading