Re: Office 2007 Deployment

bummer... Let us know what the problem was...

Pretty sure restart setting won't fix it...

have you tried it on a different test machine???

"Craig B" <CraigB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E6B8FBCA-D560-4455-BBAB-C183991FFCB1@xxxxxxxxxxxxxxxx
Blast then that exactly how i had mine with the MSP in both the root and
updates and with quotes. Other than the SMS restarts it's identical I
doubt
that is it but i will try thanks. After this I will open a ticket with MS
support

"T. Smith" wrote:

Hey there,

Yes, the " " should be in there... This is my copy and pasted command
line
on my sms server:
setup.exe /adminfile "config.msp"

I have my environment set as:
Program can run: Whether or not a user is logged on
and run with adminitrative rights.
for Requirements I have:
Estimated disk space : 2 GB
Max run time : 240 mins
Under General I have:
Run: normal
After running: SMS restarts computer ( I found this resolved a lot of
first time start up issues if the computer reboots after install)

Might be relevant... I have my .msp file in the root of my shared
office2007 directory, and also in the Updates directory. I think you can
run it without having the /adminfile "*.msp" if you have the file in the
updates directory, but I figured better safe than sorry, and it's working
for me...


"Craig B" <CraigB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DA397712-735B-4100-88F5-724D13A6F35D@xxxxxxxxxxxxxxxx
Yes running it from teh command prompt \\smserver\share etc works fine.
My
attempt at the command line from SCCM didn't. Dump question the quotes
around
"config.msp" should they have went in there?
I am uninstalling 2007 and will try without quotes

"T. Smith" wrote:

Technically I don't think you need to put in the msp in the command,
but
I
did... I don't think that's your problem...

Make sure you try running it from command prompt from the test
computer
in
question as well.

\\SMSserver\installpath\setup.exe

It could be it has problems uninstalling Office 2003.. I've had that
on
quite a few machines.. If you try uninstalling Office 2003 from add
remove
programs first, then rerun advertisement for office 2007 install does
it
work? Also, was there any beta version of Office 2007 running on the
client
in question, I've heard that can cause install problems...



"Craig B" <CraigB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:126EE0A0-D6CD-44AA-9AD8-B112E13923CC@xxxxxxxxxxxxxxxx
maybe that's my problem. My command line is just setup.exe from the
white
paper I am reading as long as you put the msp file in the Updates
folder
that
all you needed to do. I haven't ran any switches on the setup.
It's defintely not space it's a basic test machine loads of space
and 1
gb
of ram running XP sp2

"T. Smith" wrote:

Have you tried just running it from the command prompt??? It's not
a
space
issue or anything on the client side is it? It meets all min
requirements?

What if you manually uninstall Office 2003 then try running SMS
push
to
it... I've had that problem on certain machines, where uninstall
of
Office
2003 doesn't work properly from sms push of install office 2007...
When
I
uninstall manually then push app it works great on those
machines...
Some
machines prompt for the install CD when you go to uninstall office
2003
and
SMS push bombs from it...

My command line is the following and works for us (with SMS 2003
though)

setup.exe /adminfile "config.msp"

I ran
setup.exe /admin

from the 2007 cd to create the msp file... Worked great...

What's your command line?




"Craig B" <CraigB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6978D60A-8A70-4FD9-9DD4-7904A8C42DD9@xxxxxxxxxxxxxxxx
Having some issues with office 2007 deployment still in testing
phase.
I
have
pushed out other software with SCCM so I think i have the basic
procedure
down.

My test client (with office 2003 sp3 install on a xp sp2 box)
gets
the
advertisement and starts teh install but fails instantly. I have
confirmed
the client can reach the hidden share on the SCCM server with the
Office
source files. I used the OCT tool to create a MSP file placed it
in
the
Updates folder. The customization is very minor in this testing
phase
basically just putting in the key.
In the status message i get a Failure exit code of 30050 which
isn't
very
descriptive
I am not using any parameters in the command line of the program
just
going
to Setup.exe I haven't found any guidance on this if there are
switches
i
should be using.
the windows installer is pointed to the proplusww.msi file.

Just looking to do a simple upgrade for the test. Have been using
the
Deploying Office 2007 with SMS 2003 R2 guide. Haven't found a
newer
one
for
SCCM but the basics are the same, as i said I pushed out other
software
so
the basics are covered.

Any ideas?

About the only thing













.

Relevant Pages

  • RE: SMS Admin Issues
    ... SMS do NOT use GPO's to deploy the updates to the client computers. ... By default it will check update for every day but it will only install the ... "Active Directory System Group Discovery" this discovery can detect the OU ...
    (microsoft.public.sms.admin)
  • Re: Office 2007 Deployment
    ... on my sms server: ... It could be it has problems uninstalling Office 2003.. ... then rerun advertisement for office 2007 install does it ... paper I am reading as long as you put the msp file in the Updates ...
    (microsoft.public.sms.admin)
  • Re: SMS only as security patch server
    ... Or is there any way to apply automatic patch to xp-home based PC ... I pulled this from the Automatic Updates ... > install the updates the next time you start your computer. ... SMS can, but yes, you require the overhead of a domain ...
    (microsoft.public.sms.setup)
  • Re: Windows updates/office updates
    ... should be and if I have to apply any other updates? ... check if I have installed SMS 2003 Inventory Tool for Microsoft ... look for "SMS 2003 Inventory Tool for Microsoft ... So all you need do is install the latest version ...
    (microsoft.public.sms.swdist)
  • Re: Office 2007 Deployment
    ... Other than the SMS restarts it's identical I doubt ... I have my .msp file in the root of my shared ... and also in the Updates directory. ... It could be it has problems uninstalling Office 2003.. ...
    (microsoft.public.sms.admin)
Loading