Preventing users from installing software on PCs within the domain

Can I prevent a user from downloading and installing software on his own PC in a domain? If so, how? Can I also restrict a user from running software other than the one which is installed on his PC? Both scenarios are in respect to a pre-Windows 2000 environment.

    Requires Free Membership to View

    Login

If you're really talking about a "pre-Windows 2000 environment" no Group Policy will assist you. This is because Group Policy will not apply to clients earlier than Windows 2000.

However, if we expand the question, and do take into account both Windows 2000 and Windows XP, the news still doesn't get much better. Windows 2000 users can install old-style "setup.exe" software, basically, where they have access. However, the news is slightly better for Windows 2000 clients if your users want to install .MSI files. Most MSI files will be restricted from completing installation (such as Office 2000 and higher). Note, that this is 100% .MSI file dependent, and the operating system has very little to prevent it.

The news is somewhat better for Windows XP clients. If you delve into Software Restriction Policies with Windows XP clients, you'll really get fine control over which applications can and cannot run. In my book, I have nearly a quarter of Chapter 6 dedicated to Software Restriction Policies, so I encourage you to check it out.

This was first published in January 2004

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top