locked
Downgrade to Standard Version RRS feed

  • Question

  • Hello,
    
    I have OCS Enterprise installed on two servers (1front-end and 1 database). 
    No archiving. Management wants to install the Standard version all on one 
    server. Is there any documentation for doing this. Should I just uninstall 
    everything and start over? If so, how do I do the uninstall?
    
    Thanks
    Wednesday, June 4, 2008 3:24 PM

All replies

  • No downgrade possible

    OCS Standard Edition only works with SQL local on the box and does not use full SQL Server but uses the free one

     

    To uninstall Office Communications Server 2007:
    Uninstall involves performing two steps: deactivate and uninstall. These steps are outlined in detail in the Office Communications Server Deployment Guide available from the documentation download page.

    http://www.microsoft.com/downloads/details.aspx?FamilyId=760A3FF9-7F82-4A5F-841D-5E528B1DA334

     

     

    Wednesday, June 4, 2008 10:52 PM

  • No downgrade is possible.. You can install one Standard edition server. Move all users to the new OCS STD and decommission the enterprise edition.


    R. Kinker
    www.OCSPEdia.com
    Thursday, June 5, 2008 12:30 PM
  •  

    Under this scenario, I would be able remove both the SQL backend server and
    the current front-end server once the users have ben moved? Is that correct?
    Thursday, June 5, 2008 4:54 PM
  • Correct.  The Stand-Alone server will deply a local instance of SQL Express to store it's data.  Moving the users form the Enterprise server to the Stand-Alon server will relocate their DB info from the SQL backend server to the new Standalone Front-End Server.

     

    Make sure you completely remove the Enterprise pool and all associated configuration settings in AD as well.

     

    Thursday, June 5, 2008 5:05 PM
    Moderator
  •  

    OK. Thanks.

    Will I be able to see both the enterprise servers and the new standard
    server from the OCS 2007 snap-in so I can move users.


    What about  the SRV record? Can I have two of them at the same time?
    One for enterprise and one for standard?

    Friday, June 6, 2008 3:09 PM
  • Yes, each server will appear in the OCS console, but in different places.  You can move users between the servers easily.

     

    Your current SRV records should be pointing to your Enterprise pool FQDN, butI'm not sure how Automatic Configuration on clients would operate with multiple SRV records for the same service pointing to the different servers.  I'd imagine the client would only use one but I'd have to test the behavior.

     

    What I had done in the past (when transistioning users from a Stand-Alone to Enterprise server) was utilized Manual configuration (via GPO) for one server and reconfigured SRV records for the other server.

     

    Ideally you can move all the users to the new server at one time, then replace the SRV records so that all clients are directed towards the new server.

     

    If this can't all be performed in the same time window, then another possible solution would be to setup Manual configuraiton to 'hardcode' the users moved to the Standalone server.  Then once all users are moved, update the SRV record, and remove the Manual confg settings.

     

     

    Friday, June 6, 2008 3:32 PM
    Moderator

  • Multiple SRV records are not supported as per the deployment guide and moreover its not needed!

    you can delete the EE one and create one for Standard edition.. that will take care of the EE users as well..

    The OCS standard edition will route the request to the EE server if required!


    Regards,
    R. Kinker
    MCTS - LCS 2005, MCTS - OCS 2007
    http://www.ocspedia.com
    http://www.itcentrics.com/LCS_Home.htm
    Friday, June 6, 2008 4:02 PM
  • I really recommends to migrate you users from the Enterprise to the Standard Edition. Your users are not so happy when they lose their contactitems. Later on you can easily unprep your old one.

     

    Sunday, June 8, 2008 9:09 PM
  • I'm a bit confused when I get to this part of the install.

     

    I'm adding a standalone server. Eventually it will be the only server. I will slowly move users to the standalone after testing. I want to configure for automatic logons. We only have one SIP domain. If I select 'Some or all clients will use DNS SRV records for automatic logon' will that effect the users on my Enterpise server? What about "Use this server or pool to authenticate and redirect automatic logon requests'. Should I select that?

     

    Not sure what to do.

     

    7.1.  On the SIP domains page, verify that your SIP domain appears in the list. If it does not, click the SIP domains in your environment box, type your SIP domain, and then click Add. Repeat these steps for all other SIP domains that the Standard Edition server will support. When you are finished, click Next.

    8.2.  On the Client Logon Settings page, do one of the following:

    ·         If the Office Communicator clients and Microsoft Office Live Meeting 2007 clients in your organization will use DNS SRV records for automatic sign-in, click Some or all clients will use DNS SRV records for automatic logon.

    If this server or pool will also be used as a authenticate and redirect requests for automatic sign-in, then select the Use this server or pool to authenticate and redirect automatic client logon requests check box.

    Note

    When you configure automatic client sign-in, you must designate one (and only one) Enterprise pool or Standard Edition Server to authenticate and redirect client sign-in requests.


     

    ·         If the Office Communicator clients and Live Meeting 2007 clients in your organization will not be configured to use automatic sign-in, click Clients will be manually configured for logon.

    9.3.  Click Next.

    10.4.   If in the previous step, you selected Some or all clients will use DNS SRV records for automatic logon, on the SIP Domains for Automatic Logon page, select the check box for the domains that will be supported by the server for automatic sign-in, and then click Next. Otherwise, skip to the next step.

     

    Tuesday, June 10, 2008 9:34 PM
  • Hi akg414s

    Did you come right with this in the end?  I'm wanting to do the same with our OCS deployment - install a new Standard Edition server, move the users across, and decomission the Enterprise edition server.  What did you choose in the end for automatic client configuration vs. manual client configuration?  I'm worried if I choose manual configuration, that I won't be able to later enable my Standard edition server to handle authentication requests, and that clients won't be able to log in to Communicator once I decomission the Enterprise Pool.

    thanks,
    Ray
    Friday, September 26, 2008 10:39 AM
  • Hey there

    I the end i decided to just go for it and jump right in... thought i'd post my experiences here in case anyone else needs to do the same thing.

    It was really straightforward - deployed my new std. edition server, and it appeared in the OCS admin tool under Standard Edition Servers.  During configuration, I specified that the new Std. Edition server will accept client authentication requests, and that clients would be configured for automatic login.  Once setup completed, I found that everything still worked perfectly for existing connected users (even if I got them to sign out and try sign back in, all worked fine).  I then moved my own account from the Enterprise pool to my new Standard server using the Move task within the admin console.  I signed out of Communicator, and was able to sign in successfully right away.  It seems that OCS does indeed redirect requests the server that hosts your account.  I then moved ALL our users across to the Std. server, updated the DNS SRV records, tested, and then decomissioned the Enterprise pool.   To do this I deactivated each server role using this doc - http://technet.microsoft.com/en-us/library/bb936625.aspx.  I then removed the Enterprise pool, and uninstalled all the OCS components from add/remove programs.

    Everything seems to be working fine, and OCS is much more stable and sign is a lot faster - must've had some gremlins on our old Enterprise server.

    Hope this helps someone out there  ;-)

    cheers
    Ray
    Friday, September 26, 2008 7:15 PM
  • Raymond,

     

    I'm curious as to where you had the Web Components installed and did you move your Address Book files over to the new server?

     

    Friday, September 26, 2008 7:47 PM
    Moderator
  • Hey Jeff

    The web components were also on the Enterprise server.  I didn't move the address book files over.  Hope i haven't messed up on that one - we weren't using federation and we have a script running every night to generated everyone's contacts, so I don't think we would've lost anything?  All we're using OCS for is IM, am not at all clued up on any of it's other features... hope i didn't break it?  ;-)

    cheers
    Ray
    Friday, September 26, 2008 8:54 PM
  •  Raymond Diack wrote:
    Hey Jeff

    The web components were also on the Enterprise server.  I didn't move the address book files over.  Hope i haven't messed up on that one - we weren't using federation and we have a script running every night to generated everyone's contacts, so I don't think we would've lost anything?  All we're using OCS for is IM, am not at all clued up on any of it's other features... hope i didn't break it?  ;-)

    cheers
    Ray

     

    You would not have lost anything, you are safe.  When users sign in next, an updated version of the ABS files will be downloaded to the client profile, so no sweat.

     

    If you want to test, delete your abs files from your client profile, then end the Communicator process, then restart it and sign in.  Wait a min and you should see the new file in your profile being pulled down.

     

    ABS is installed automatically, so I highly doubt you messed anything up, but at least do yourself a favor and test it out before users hit it.

    Saturday, September 27, 2008 2:06 AM
  • Hey deathjester - whew glad to hear that.  Yesterday i tested with 4 different users, and didn't notice anything strange with the address book, so I'm sure it's fine. 

     

    thanks,

    Ray

    Saturday, September 27, 2008 10:37 AM