Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
SBS 2003 to SBSE 2011 Migration Failed so I did it manually, all is perfect now but Dashboard not working.

Unanswered SBS 2003 to SBSE 2011 Migration Failed so I did it manually, all is perfect now but Dashboard not working.

  • Tuesday, May 15, 2012 4:49 AM
     
     

    Okay,

    The migration failed from the SBS 2003 box. I had gone into the logs and dcpromo was failing so brought up the task manager and kill the migration wizard. I transferred all 5 FSMO roles and I was able to transfer everything else and the AD was fine, so I dcpromo the old box and took it off the network. I set up the DNS on the SBSe box and I set up DHCP on the router.

    DCdiag has no errors and I was able to setup my shares and verify my users, but when I try to launch the dashboard I get

    "You have not finished setting up Windows Small Business Server 2011 Essentials. You cannot open the Dashboard until you complete the server setup."

    So is there a way or a registry entry that I can modify to let SBSe know that I'm done with the setup so that I can launch the Dashboard?

All Replies

  • Tuesday, May 15, 2012 9:55 AM
    Moderator
     
     

    Did you backup the Certificate authority as the documentation explains?

    Part of the migration process is to restore the CA and import certificates to the dashboard, using PowerShell.


    Robert Pearman SBS MVP (2011) | www.titlerequired.com | www.itauthority.co.uk

  • Wednesday, May 16, 2012 1:13 AM
     
     

    I think that you are on to something, I did back up the certs but I think some thing went wrong. When I try to add the cert I get this.

    PS C:\Program Files\Windows Server\Bin> add-wsslocalmachinecert
    Add-WssLocalMachineCert : CCertRequest::Submit: The parameter is incorrect. 0x8
    0070057 (WIN32: 87)
    At line:1 char:24
    + add-wsslocalmachinecert <<<<
        + CategoryInfo          : NotSpecified: (:) [Add-WssLocalMachineCert], Arg
       umentException
        + FullyQualifiedErrorId : System.ArgumentException,Microsoft.WindowsServer
       Solutions.Administration.AddLocalMachineCert

    And when I try to add the users to the dashboard I get this.

    PS C:\Program Files\Windows Server\Bin> Import-WssUser -Name Chris
    Import-WssUser : Connect
    At line:1 char:15
    + Import-WssUser <<<<  -Name Chris
        + CategoryInfo          : NotSpecified: (:) [Import-WssUser], UserExceptio
       n
        + FullyQualifiedErrorId : Microsoft.WindowsServerSolutions.Users.UserExcep
       tion,Microsoft.WindowsServerSolutions.Administration.ImportWssUserCommand


    • Edited by gretti Wednesday, May 16, 2012 2:50 AM
    •  
  • Wednesday, May 16, 2012 4:58 AM
    Moderator
     
     

    Hi,

    This issue occurs if you changed the system time to a time that is earlier than the installation time, the Windows Server services cannot start because the certificate appears as expired. The Windows Server Solutions Servers depend on this certification.

    To fix this issue:

    From the server
    1. Ensure that the date and time settings shown in the system tray are current.
    2. Visit Windows Update to download and install all critical and important updates.
    3. Restart the server.
    4. After restarting the server, click Start, type mmc.exe, and then press ENTER. An empty management console appears.
    5. In the management console, click File, and then click Add/Remove Snap-in.
    6. In Add or Remove Snap-ins, in the list of available snap-ins, select Certificates, and then click Add.
    7. In Certificates Snap-in, select Computer account, click Next, and then click Finish.
    8. In Add or Remove Snap-ins, click OK.
    9. In the management console, expand Certificates (Local Computer), and then click Trusted Root Certification Authorities.
    10. In the details pane, right click Certificates, point to All Tasks, and then click Import.
    11. In the Certificate Import Wizard, browse to %programdata%\Windows Server\Bin\WebApps\Site\Resources, click CAROOT.CER, and then click Open.
    12. In the Certificate Import Wizard, click next Next until you reach the Completing the Certificate Import Wizard page, and then click Finish.
    13. Restart the server.

    From client computers
    • Ensure that the date and time settings shown in the system tray are current and that they are the same as the server settings.

    Notes:
    • If the date and time reverts to an invalid time after you restart the server, check the BIOS settings to ensure that the BIOS time is set correctly.
    • If your server is running Windows Small Business Server 2011, this problem will be fixed automatically when you restart the server because the certificate is stored in Active Directory.
    • A certificate backup file is created during server installation. If you remove the certificate backup file, your system may not function correctly. If this occurs, you should perform a clean installation to recover the server.

    For the detailed information, please refer to the following Microsoft TechNet article:

    How to Repair Certificate Issues in Windows Small Business Server 2011, Windows Home Server 2011, and Windows Storage Server 2008 R2 Essentials
    http://social.technet.microsoft.com/wiki/contents/articles/3940.repair-certificate-issues.aspx

    Regards,


    Arthur Li

    TechNet Community Support

  • Wednesday, May 16, 2012 5:30 AM
     
     
    So, all the Certs are there in the MMC console including the cert from the old server. Are there any other ways to get the Dashboard to work?
  • Wednesday, May 16, 2012 7:48 AM
     
     

    Thank you for responding

    The time was correct in the BIOS when I installed SBSe but I was following your instuctions and I ran in to a problem. %programdata%\Windows Server\ does not exist. There is a "program files\Windows Server\Bin\WebApps\Site\Resources" but there is no CAROOT.CER file there, or anywhere on the drive.

    I have followed the instrutions here http://support.microsoft.com/kb/2578298

    But I'm still getting the power shell error.