ceh329 Posted August 22 Share Posted August 22 Hello, I need to upgrade our on-prem Win 2012 severs to 2019 in order to support the latest version of WS1 UEM. Does anyone have any experience or gotchas that might impact WS1 UEM by doing an in-place upgrade of Windows Server? Quote Link to comment Share on other sites More sharing options...
Employee Victor León Posted August 22 Employee Share Posted August 22 Hello, It is not recommended to perform an in-place upgrade of the operating system of a server. Instead, I recommend that you build a new instance of WS1 UEM server in parallel. 1 Quote Link to comment Share on other sites More sharing options...
ceh329 Posted August 22 Author Share Posted August 22 Ok, I dont have that option available to me. What are the possible issues of this and why is it not recommended. Quote Link to comment Share on other sites More sharing options...
Employee Siddesh Raj Patil Posted August 23 Employee Share Posted August 23 Hi , One thing you have to ensure is that you do not have AirWatch installed on the drive which contains your OS . If you do make sure you are keeping a backup of all the files when you carry out the server OS upgrade. Also If you have an option to build a new Win 2019 server to host WS1 UEM then migrating from the exiting server to the new one would be simpler. Regards, Siddesh 1 Quote Link to comment Share on other sites More sharing options...
StephenWagner7 Posted August 23 Share Posted August 23 17 hours ago, ceh329 said: Ok, I dont have that option available to me. What are the possible issues of this and why is it not recommended. There's numerous reasons why in-place upgrades are not recommended. This isn't specifically because of WS1, but generally recommended against in the IT industry as a whole. It's always best to deploy new servers with the updated operating systems, and migrate the applications over. Forgetting about WS1, and just talking in general, services may fail, or the service start order may be skewed, you'll probably have issues with some or most of your 3rd party applications, and some applications may simply not make it through the upgrade process. 2 1 Quote Stephen Wagner (President, Digitally Accurate Inc.) VMware vExpert (vExpert Pro, vSphere, vSAN Awards), Omnissa Tech Insider, NVIDIA NGCA Advisor, VMUG Leader, and Director (Board of Directors) at World of EUC Check out my Tech Blog: https://www.StephenWagner.com Link to comment Share on other sites More sharing options...
Employee Daniel Langley Posted August 23 Employee Share Posted August 23 (edited) One of the conveniences of the WS1 architecture is that the consoles are 'dummy' servers that require a DB. You can deploy a new VM with appropriate OS and simply install the WS1 UEM bits on it and connect into the existing DB and you're good to go. Edited August 23 by Daniel Langley 1 Quote Link to comment Share on other sites More sharing options...
Employee Hussam Rabaya Posted August 28 Employee Share Posted August 28 you can t grantee all windows servers will work after in place upgrade in such cases , if you have high- availability servers (e. g. more than 1 console server ) , its safe to do : -take backup -remove one one of the nodes from load balancer - re-build it with new OS -do UEM installation and patching with same old version (e.g console , DS, ENS. ACC,.....) - return it back to load balancer -repeat to the remaining Quote Link to comment Share on other sites More sharing options...
Simon Frankiewicz Posted Monday at 09:37 PM Share Posted Monday at 09:37 PM Do you have a path for updating Workspace ONE Assist. Because I plan to upgrade the OS version, and I don't know how the application will behave after the version change? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.