J
JHO
Hi Everybody,
I have a specific question about how Office 2007 installs itself when it is
deployed from Group Policy. At present, my setup is to have the machines
automatically installed with XP using RIS and then applications installed
automatically through the use of Software Installations and Group Policy.
If I install the software normally once the machines have been installed
with XP, the notice "Configuring Microsoft Office 2007" comes up and modifies
what is installed through the config.xml- adding and removing components as I
need them.
My problem is that this process ONLY occurs if NOTHING else is running at
the time. If it cannot run, then the software that I specify to NOT install
with show in the start menu, and the other apps are not installed. In my
setup, I am using the DriverPacks from driverpacks.net so that the video
drivers and hardware on all of my machines are kept up to date.
Unfortunately, it uses RunOnceEx to finish this process and add the drivers
to the system folder, meaning that the Office 2007 Customisation never seems
to run.
What SHOULD happen with this type of installation is that nothing should
conflict- RunOnceEx should run before the logon screen. However, using RIS,
RunOnceEx only runs after the first interactive login, hence the conflict and
non-installation.
This seems to be a bug with RIS that will cause ANY post-installation
settings coming from RIS to block the installation of Office 2007 editions
deployed through Group Policy.
My Question is this- is there either a way to postpone the customisation of
Office 2007 until after a second or third reboot? Whilst this is the wrong
place to ask, does anyone know whether RunOnceEx can be postponed or if there
is a place even before the first logon which could run this 'finisher' or
other installers?
Thanks in Advance!
I have a specific question about how Office 2007 installs itself when it is
deployed from Group Policy. At present, my setup is to have the machines
automatically installed with XP using RIS and then applications installed
automatically through the use of Software Installations and Group Policy.
If I install the software normally once the machines have been installed
with XP, the notice "Configuring Microsoft Office 2007" comes up and modifies
what is installed through the config.xml- adding and removing components as I
need them.
My problem is that this process ONLY occurs if NOTHING else is running at
the time. If it cannot run, then the software that I specify to NOT install
with show in the start menu, and the other apps are not installed. In my
setup, I am using the DriverPacks from driverpacks.net so that the video
drivers and hardware on all of my machines are kept up to date.
Unfortunately, it uses RunOnceEx to finish this process and add the drivers
to the system folder, meaning that the Office 2007 Customisation never seems
to run.
What SHOULD happen with this type of installation is that nothing should
conflict- RunOnceEx should run before the logon screen. However, using RIS,
RunOnceEx only runs after the first interactive login, hence the conflict and
non-installation.
This seems to be a bug with RIS that will cause ANY post-installation
settings coming from RIS to block the installation of Office 2007 editions
deployed through Group Policy.
My Question is this- is there either a way to postpone the customisation of
Office 2007 until after a second or third reboot? Whilst this is the wrong
place to ask, does anyone know whether RunOnceEx can be postponed or if there
is a place even before the first logon which could run this 'finisher' or
other installers?
Thanks in Advance!