Windows Server 03 migrations are like oil change for your car. You know that you need to do them, and the longer you wait, you can have more at risk.
I know what you're saying. They say: "... I know I have to do it Frankly I know that but I do not know where to start, and it is a difficult task"
Do not be afraid , my friend, you follow these simple steps and you will be well on a modernized solution on your way.
Step 1: No app behind
hasleft in the last 13 years, we have more applications than we could possibly count amassed. And we know some with Server 2012 R2 might not be compatible, the latest versions of Internet Explorer, App-V and more. We're pretty sure we applications, which we do not even know, because they are so old and so dark that only Milton Waddams and his red stapler still use.
And yet we have a formulated plan, which answered to the line of business.
Instead of relying on hunches and guesses, I could suggest a pretty little tool called AppDNA? Just show AppDNA to your.MSI or EXE binaries and application libraries and allow his discovery and analysis engine to read the DNA of your apps (marketing genius, right?). Like a well-trained doctor an MRI examination AppDNA will conduct a thorough analysis and spit out detailed reports of green apps (compatible with all your destinations), red apps (problem child) and Amber apps (will work after some tweaking). Like a good doctor, it's also prescribe medication to fix it, or refer you to specialists where necessary.
Now you can prioritize a comprehensive plan project and which applications can be most easily migrated and which applications will require more effort. Heck, in many cases, simply click on the "Fix It" button on AppDNA itself and you can be done with it
Step 2: Get up and deliver
Now that you your app migration project plan in place, it's time to start the migration process. To minimize the impact on users you can have a Windows Server 2012 R2 are on and then add XenApp 7.6 on top. Take the applications that have been flagged by Green AppDNA and publish them to test users. Once your User Acceptance Testing has been completed, you are ready to use the updated app delivery to your entire population. With XenApp 7.6, you just go ahead and publish it to more and more users, have again instantiated without.
In the case where you have applications that plug into 32-bit country, you could possibly be made up a Windows Server 08 and lagging by 14 January 2020, if this version of its extended support corresponding date. I see it as the minimum balance on your credit card paid each month. Not a great solution, but you could buy some time
Step 3 :. Movin 'on up
Well, what reputable blog in 2015 ends without a reference to the "cloud"? As with any migration or modernization project, the cloud is completely ease your allies future migration.
Using Workspace cloud services can displace existing or new workloads to the cloud, transparent to end users. Workspace cloud is developed with the same 25 years Citrix philosophy that customers should have a complete range of platform. Perhaps Azure right for workload A is today, but tomorrow you will Amazon Web can use cloud with Citrix XenApp and workspace for Workload example, allow you the freedom of any cloud platform and you can start today.
[1945006ImvergangenenMonat] I ran an on-demand webinar that goes into more detail. In case you missed it or want to see it again, here is a link.
So what are you waiting for? Contact is maintained for a smooth migration away from the risk of obsolete infrastructure Citrix rep today. And while you're at it, get the oil changed in your car.
0 Komentar