Pushing updates to wireless users

Pushing updates to wireless users

What can a company use to ensure deployment of software updates, virus signatures and patches to users with wireless connections?

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Wireless access is not really the problem. You have this problem for all users on your network. For computers in your local space that are hardwired, you can set them up for automatic updating, or run around and update them all manually when you need to. It is difficult to run around and apply updates to remote users whether they use wireless, dial-up or Internet connection.

What you need is a desktop management system, such as Microsoft's SMS or CA's Unicenter. As noted in other answers, mention of a product name does not imply endorsement. There are many such products in this line of software and you should do your own evaluation to determine which is best for your own application.


For more info on this topic, please visit these SearchSecurity.com resources:
  • Best Web Links: Infrastructure and network security
  • Featured Topic: Best practices for patch management
  • Security Policies Tip: Issues to address in your incident management policy

    This was first published in February 2004