Deployment Lock Down

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Deployment Lock Down

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Application Deployment >> Deployment Lock Down

Page: [1]

Message

<< Older Topic Newer Topic >>

Deployment Lock Down - 6/5/2008 3:18:08 PM

rgood

Posts: 4
Score: 0
Joined: 6/27/2007
Status: offline

I am running into a number of issues where users are using their machines as an advertisement is pushing an update package or they interupt the install somehow. What are some solutions that I could use to lock the machine down at logon so the advertisement can run freely then reboot the machine if necessary without the user getting access to the OS?

Windows XP Pro machines on AD 2003

Post #: 1

RE: Deployment Lock Down - 6/9/2008 10:51:43 PM

rbennett806

Posts: 784
Score: 13
Joined: 6/14/2006
Status: offline

Is "locking" the machine going to fix your problem, or create more problems when the users start screaming that they can't work because they can't log in? I think the best method is to use Wake-On-LAN to try to do the majority of the installs during off hours. After that I think it's better to put up a splash screen to show the user that something is being installed so that they are aware that they shouldn't shut down the machine or to help explain to them why it's running slow. Of course that's just my own two cents.

If that doesn't answer your question you might want to post in whatever forum it is that corrponds to the technology you're using to push things out (SMS 2.5, SMS 2003, SCCM, etc...) and someone might be able to get you a more solid answer once they know what your backend structure is like...

(in reply to rgood)

Post #: 2

RE: Deployment Lock Down - 6/20/2008 8:18:48 AM

ChrisR

Posts: 40
Score: -2
Joined: 6/19/2008
Status: offline

As said, either have the installer throw up a splash screen so that the users can see anything that's happening, or do the opposite and make it totally silent.

Unless it's just the fact that logging on in itself stuffs things up? In which case might be better to look at another way to deploy apps.

(in reply to rbennett806)

Post #: 3

RE: Deployment Lock Down - 6/20/2008 5:32:32 PM

jsandys

Posts: 463
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline

I have never seen this as a problem in any production environment (and I have seen a lot). SMS/ConfigMgr is by far the most robust way to deploy apps in a Windows environment and has been so for almost 10 years.

Can you be more specific about the issues that you are seeing? Are people rebooting systems? Are they opening taskman and killing things? Are all of your users local administrators (kill me now)? Why are you deploying software during business hours?

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to ChrisR)

Post #: 4