RE: SMS Deployment of Office 2007: Silent w/o user interaction con



I understand, I have many laptop and remote users across the state. Manly
only login with VPN. Sometimes it takes a week to push a new software
packagea to them but thats ok. I admit there are some limitations to the
current framework but I have written software and policy to adapt to it. We
have a easy reason to use SMS. It is pretty much free for us.
--
-----------------------
http://sms-hints-tricks.blogspot.com/


"jon" wrote:

That briefs well, but try taking a domain with predominantly mobile users
spread out across 35 offices (mostly laptops), and get all of them to stay
powered on (not hibernating / shutting down automatically) overnight for one
night (much less a week or so to spread out the deployment).

I get more and more discouraged everyday I use SMS. WSUS 3 handles software
updates MUCH better (IMHO), Group Policy handles software deployment better
(at least from the user experience)...I'm running out of reasons to keep SMS
going! If it weren't for collection and reporting, this product is pointless
for me.

I certainly hope some of these issues are resolved in the next release! I
have to believe that sysadmins want t be able to control when and how
software is released with a very granular level of detail...

(climbing down off my soapbox now)

"Matthew Hudson" wrote:

This is a problem that many people, including myself have a problem with.
The only solution is to wake the computers or just have them on and install
like at 2am or a window when you know you have complete control. I have had
several packages that require no use to login, but then a user comes back and
logs in ,the packages is interrupted by the logon, or it forces a restart but
since SMS only checks for the logon condition at the very very beginning of
the adv, there is a problem. I know someone talked about creating a software
plugin to check for the status and not allow the user to login if sms is
doing something. Sorry there isn't an answer right now but know that it is
an issue and people are trying to solve it. I don't know if this is an issue
in the new sms. We have Office set to install totally silent so no splash
screen or user interaction is seen.
--
-----------------------
http://sms-hints-tricks.blogspot.com/


"jon" wrote:

All,
I'm testing deployment of Office 2007 in our environment which already has
SMS R2 installed and working. I already have the package (and .msp)
configured, and it works great and is completely silent...it uninstalls 03,
then installs 07.

The issue is controlling the deployment so users don't have the ability to
screw it up! I can set the advertisement to only run when no user is logged
on, but if it starts running, and a user logs on in the middle of it and
opens office 03 (before it's uninstalled)...it's destroyed.

I can set it to run at logon (which I expected to work like software
deployment through group policy where the user only sees "installing office
2007", and doesn't even see a desktop until it's done), but that just makes
the trigger for starting a user logon.

Is there a way for me to deploy this where the computer will reboot, and
install on reboot? (not allowing a user to logon until it's done)?

I have to believe this is possible...if not, why wouldn't we just use group
policy? (the only reason I can see is the use of BITS...which is why we're
using it...)
.



Relevant Pages

  • RE: SMS Deployment of Office 2007: Silent w/o user interaction con
    ... night (much less a week or so to spread out the deployment). ... I get more and more discouraged everyday I use SMS. ... The only solution is to wake the computers or just have them on and install ... logs in,the packages is interrupted by the logon, or it forces a restart but ...
    (microsoft.public.sms.swdist)
  • Re: Questions Deploying Office 2007
    ... During our discussions about deployment, ... I'm ok with SMS using the 'setup.exe' command to run the program. ... All of our SMS clients have a 2GB cache. ... additional program components (i.e. Install on Frist Use)? ...
    (microsoft.public.sms.admin)
  • Re: Questions Deploying Office 2007
    ... During our discussions about deployment, ... I'm ok with SMS using the 'setup.exe' command to run the program. ... additional program components (i.e. Install on Frist Use)? ... folder on the client. ...
    (microsoft.public.sms.admin)
  • Re: General Advice on performance
    ... At the moment we haven't released SMS yet so most people are still using ... Novell's unattended install method to remove the client. ... expect deployment to start a little after the client is installed and has ...
    (microsoft.public.sms.swdist)
  • Deployment of Office 2003 or any apps for that matter
    ... The big deployment will be for Office 2003 Pro on Windows XP SP1, ... had SMS) yet. ... We will then make a .BAT file to make a call on the MSI to ... Does someone need to be logged in to install? ...
    (microsoft.public.sms.admin)

Loading