Planning Enterprise Desktop Deployments: Part 2
In Part 1, we looked at ways to collect information about your hardware and application estate. Now you have this information what can you do with it? We specifically look at your application estate.
Planning Enterprise Desktop Deployments: Part 1, Part 2
Now we have used ACT described in part 1, what exactly can we do with this information? The most important thing you can take from this information is the simple fact that your clients have reported to you what is installed, if you take part in the community exchange you also know from a community level if these applications are compatibility with Windows 7 or not.
Many companies can relate to this statement: “We have multiple products which do the same thing”. I have been to various companies and they all agree with the same statement. A deployment project is a chance to be able to review your applications, rationalise your application estate and create a corporate portfolio of software which your users can request.
Developing a standard portfolio of applications can reduce your licensing costs, a recent customer was interested in this because they had five different FTP clients in their estate when actually one is perfectly fine. Some of these applications were licensed as well. Resolving this issue with the users, speaking to them and finding out what they use it for and then you can determine which product you can use as your standard.
The idea behind using your application portfolio and adding it into your standard framework, often called a standard operating environment or SOE means you can start to develop standards, processes and procedures to help keep your estate healthy and keep productivity high.
In your framework you will want to define what will be in your core image, will it be a thin image with no applications? A thick image with all your corporate applications installed? You can also use your deployment project to review policies such as your IT security policy, systems policy and storage policy to make sure these documents will still apply to the new environment.
Also use this chance to look at your use of folder redirection and roaming profiles, can you implement them if you don’t use them already, can you change how you use them to make your environment more effective? All these questions are important while developing your framework which will be important to a successful deployment.
Finally, think about your actual image configuration, make sure it is properly configured for the enterprise environment, does your image exclude games for instance, any features such as Internet Printing should be turned off for the enterprise. These are all again important things which need to be considered when you are planning your deployment.
So in summary, look at rationalizing your application portfolio, if you have less to support it will cost less, this is a simple fact. Also look at documenting your image and reviewing your policies, this will be important for later in the deployment process.
This completes part 2, but in part 3 we will be looking at the technology available to you for your deployment and why using it to plan a proof of concept environment is important.