cancel
Showing results for 
Search instead for 
Did you mean: 

Standard Desktop Project

henderson1977
Grafter
Posts: 191
Registered: 31-07-2007

Standard Desktop Project

Hi all

I work in IT for a global law firm and am involved in a Unified (or Standard) Desktop Project. The aim of which is to consolidate the various desktop configs 'in the wild' to a more manageable solution that reduces pressure on the IT Support function.

We know we need to carry out a software and hardware inventory to determine what is 'on the shop floor'. We know we have many decisions to make with regards the choice of applications, virus scanner, VPN client, etc...

Does anyone have any experience of such a project or task? I would be interested to hear your ideas/suggestions/recommendations.

Thanks in advance
Scott
3 REPLIES
N/A

Standard Desktop Project

3 time saving ideas in a windows domain

1) create a company standard profile, then use domain manager/AD to set everyone to use this profile (set permissions to apps/files accordingly) (or you create profiles for seperate departments etc) either way is doable

2) Revise up on ghosting and remote deployment techniques, create a standard pc which has all the apps on, but only people with certain permissions can access certain apps, such as sage only allows accounts people, and stores can access a stocktaking app such as wasp
SMS server is useful for inventory and seeing what is installed on the network
A evaluation copy from microsoft is available through CD or download

3) Revise up on group/local policies, to stop people installing rubbish on there PCs, also put firefox or even opera, set IE to be an app which they cant open through a policy (or not if they depend on it for an application, then just delete the shortcut)
Also stop most of the non essential services running
That way you wont need to worry as much about virus
Block access to the control panel to only users who need it such as helpdesk or admins to avoid people messing about, oh and the registry should be locked out as well

4)Use Remote assistance/access tools, such as daimeware, realVMS etc, install these on the standard image, will save hours of helpdesk/support time
They usually can be set so only certain IPs can be used to connect to them

Your best bet is to get two PCs and one server in a mini test domain
Then Get a list of all the apps needed, the different user groups and what needs to be running.
Then play around with policies, images and access rights
Once all this is done on the test domain, and is fully tested the deployment to the network will prob be a weekend job
A day or two later the calls should die down as all the bugs are fixed and then you can start having fun with the VPN side and start building up the network
N/A

Standard Desktop Project

The above are good suggestions if all pc are the same. I worked for a bank with 30,000 users creating the desktop and if you have a variety of pc's with different video cards memory etc you have problems.

You will have to create a ghost image which has sysprep run on it or use RIS server. You should have a standard image with things like Office etc on. The rest you can use profiles to supply specific apps and install them via AD or you can use ZAP files for small apps. Remember if you lock down the pc you must by law let them change screen res and the mouse.

We built a standard pc with office etc on it and then if you use acronis you can install other apps and create a backup image which you can use to update the pc which need other apps adding
henderson1977
Grafter
Posts: 191
Registered: 31-07-2007

Standard Desktop Project

Thanks to you both, kevicho and mwight. Very useful advice/suggestions. A decision was made to use LANDesk for imaging, software license monitoring, etc... so I'm creating a PXE Boot Menu and testing speed/performance/issues... all good so far. Although we did have a mup.sys error after imaging a machine using LANDesk OSD, we did find a resolution in relation to mass storage controller. Just need to download ALL XP drivers for our various hardware platforms and then test driver injection....

Thanks again!

Scott