A
Adrian Marsh (NNTP)
All,
I'm trying to deploy Office 2K via Active Directory coputer GPO, from an
Select Admin network share.
I've setup my transform to install the whole product locally (clients
are laptops).
I point the AD Software Installation GUI to the office MSI, and add the
MST transform file as well.
I apply these settings, wait 5 mins, and then I power up the test
client. Office seems to deploy (I see the "installing" message before
logon, and it takes a v. long time).
Before starting any application, or even logging in, I pull out the
network connection (simulating "road usage"), login and try to start Word.
But then, instead of Word, it starts the MSIinstaller, and tries to
access the Admin share - which is obviously not there, so it complains.
Same goes for any other Office app.. ARGGH!!
If I rebuild the laptop (ghost) to a pre-office version, clean up AD to
take off Office, then login and manually run "setup.exe
/TRANSFORM=testing.MFT" from the same admin share, and then replicate
the test (disconnect network and start Word), then it doesn't have the
same problem.
So have I missed something in AD Software Install ??? Is there some
further setting I need to put in ?
I don't really want to have to deploy using setup.exe, as then it'll be
difficult to manage future upgrades etc.
This is driving me a bit nuts, as I thought SI was supposed to help, not
hinder.
Adrian.
I'm trying to deploy Office 2K via Active Directory coputer GPO, from an
Select Admin network share.
I've setup my transform to install the whole product locally (clients
are laptops).
I point the AD Software Installation GUI to the office MSI, and add the
MST transform file as well.
I apply these settings, wait 5 mins, and then I power up the test
client. Office seems to deploy (I see the "installing" message before
logon, and it takes a v. long time).
Before starting any application, or even logging in, I pull out the
network connection (simulating "road usage"), login and try to start Word.
But then, instead of Word, it starts the MSIinstaller, and tries to
access the Admin share - which is obviously not there, so it complains.
Same goes for any other Office app.. ARGGH!!
If I rebuild the laptop (ghost) to a pre-office version, clean up AD to
take off Office, then login and manually run "setup.exe
/TRANSFORM=testing.MFT" from the same admin share, and then replicate
the test (disconnect network and start Word), then it doesn't have the
same problem.
So have I missed something in AD Software Install ??? Is there some
further setting I need to put in ?
I don't really want to have to deploy using setup.exe, as then it'll be
difficult to manage future upgrades etc.
This is driving me a bit nuts, as I thought SI was supposed to help, not
hinder.
Adrian.