We help IT Professionals succeed at work.

Lync  Server 2010 Uninstallation

I recently install a trial version of Lync Server 2010 and deployed it to roughly 15 users in the environment.  I would like to uninstall it, and then re-install properly, and deploy to the entire company.

What is the proper procedure to uninstalling, and re-installing?  Are there any i, implications or issues that may be caused by doing this?
Comment
Watch Question

I assume this was just a standard installation.

Is it a VM or physical box?
Did you get certs?
Did you extend the Schema, Forest and Domain in your AD Environment?

Author

Commented:
Yes, it is a VM, and Standard Edition install

I created a self-signed cert via IIS on the Lync Server

Yes, I extended the schema, forest, and domain.
ok, so no external access at this point?

Author

Commented:
no
ok, then this should not be too bad.  There is a formal process for uninstalling Lync which can be seen here:

http://terenceluk.blogspot.com/2011/01/step-by-step-instructions-for.html

However, since this was a test and you are using a VM with no external certs, then it is much simplier.

I would disjoin the server from the domain, thus removing DNS (assuming you are using AD integrated DNS) and LEAVE the schema, forest and domain extensions, especailly since removing them is a pain and you would jsut have to redo it :-).

Once done, I would uninstall the Lync clients and remove the folders from the users profile (although not needed, I am just over cautious).  Next spin up a new server, place a working, licensed version of Lync on it, attach it to the domain and go through the same process you did with the trial.

The takeaway here is that it was trialware, with no external connections.  I had something similar happened and the easiest solution was deleting the entire server farm (I have enterprise) and repointing the DNS to the new servers.

Hope that helps!

Author

Commented:
Ok, will it be an issue if I name the new server the same as the trial server?
It should not, becuase you are wiping out DNS entries.  I also believe that when you re-setup you will request a new cert so that shouldn't be a problem either.

Me personally, I would name it something else just to be sure but this should work.  The other option is to follow the directions in that article and that should work to.

Author

Commented:
If I follow your instructions, rather go through that huge document, is there any chance I will have issues or errors when trying to install again?  I have 2 days to get this installed properly, and cannot afford issues......
I cannot guarentee it but this was my situation, what I did and the outcome....

I created an Enterprise rollout with an FE, SQL Back End, Monitoring and Arch server, Director and Edge Server.  I built the topology, added the DNS, added the internal CA cert and all was good..... until i noticed I spelled the sip domain wrong and you cannot change this once you publish.  This was all done on VMs.

So what I did was disjoin all the servers attached to the domain (FE, BE, Monitoring/Arch and Director) and then rebuilt them all with different names.  I redid the topology and all worked perfect.

I beleive I was over doing it.  i think I could have gotten away with the same names, but with stuff like that, you may not know until later.  But this worked for me.  The thing is, I, like you, was not in production, I had to move kind of quick and I didn't want hooks, that is why I renamed it all.

Hope that helps

Explore More ContentExplore courses, solutions, and other research materials related to this topic.