Re: SBS 2003 - SBS 2008 migration issues

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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: Printer autocreation failing
    ... behaviour of a TS incompatible printer driver. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Tried installing that printer tray hotfix, ... Also tried updating the RDP client to the latest ...
    (microsoft.public.windows.terminal_services)
  • Re: Printer autocreation failing
    ... reinstall the driver onto the TS box). ... Check in Printers and Faxes - File - Server properties - ... Also tried updating the RDP client to the ... box and installing the print queue from the remote server ...
    (microsoft.public.windows.terminal_services)
  • Re: Printer autocreation failing
    ... redirection of the driver to the LJ4) and functional. ... Check in Printers and Faxes - File - Server properties - ... Also tried updating the RDP client to the ... box and installing the print queue from the remote server ...
    (microsoft.public.windows.terminal_services)
  • Re: .webpnp Driver file
    ... I think the client user will need to be an admin user if the driver contains ... Server is able to create webpnp file. ...
    (microsoft.public.windows.server.clustering)
  • Re: SBS 2003 - SBS 2008 migration issues
    ... If I remove the hyper V, will it "unhork" the wizards? ... because the virtual network connection confuses the wizards? ... before you start and this will be client connectivity disruptive. ... driver and the cleints being 32 bit OS's. ...
    (microsoft.public.windows.server.sbs)