OK, I'll try that when I get back to work next week and see what happens.

Hi,

Please inform the results.

Thanks

I can get it to install, but I can't get it to recognize when Visio and /or Project are already installed and not run again if not needed.

This is the login script I'm using for Visio 2010.  I just substitute the work Visio for Project to make a login script for Visio.  

It works but the part where it is supposed to recognize that the product is already installed and not install again doesn't work.  can you see an error or other reason why?

setlocal


REM *********************************************************************
REM Environment customization begins here. Modify variables below.
REM *********************************************************************


REM Get ProductName from the Office product's core Setup.xml file, and then add "office14." as a prefix. 
set ProductName=Office14.Visio


REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\server01\userapps\VisioPro2010


REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\server01\userapps\VisioPro2010\Visio.WW\config.xml


REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\server01\userapps\VisioPro2010\logs


REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************


IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)


REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if NOT %errorlevel%==1 (goto End)


REM Check for 32 and 64 bit versions of Office 2010 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS) 
:ARP86
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if %errorlevel%==1 (goto DeployOffice) else (goto End)


REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt


REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End


Endlocal

• Edited by MyGposts Friday, March 16, 2012 5:48 PM

I found that the Project script wasn't working properly to recognize it was already installed because the productname is prjpro, not project.

Does anyone have a different  suggestion on how to install multiple applications by logon script?

We don't ALWAYS install both Project and Visio.  Some people only need one or the other.

I need to find a way to make it install this way.

If the user belongs to the Visio group, install Visio once. If the user belongs to the Project group, install Project once.  If the user belongs to both groups, install Visio, wait for the installation to complete and then install Project.  

Can this be done?

The software installations from each script would interfere with each other when the user is added to both groups and when I set a policy to make logon scripts run synchronously, it caused the logon to the desktop to hang even when there was no software being installed.  

I suppose I could make a third security group called "VisioandProject" and put the users that need both into that security group and then use login script that installs both Visio and automatically launches the Project installation as additional software as suggested above, but that seems more convoluted than it needs to be and will cause confusion. 

• Edited by MyGposts Tuesday, March 20, 2012 12:20 AM

Did you ever solved this issue MyGposts?

I just ran into the same thing today.  I added: timeout /t 480 to create a pause for 480 seconds to one of the scripts.  It's working for me.

This may be some kind of WinPE related issue because we have had second problem ever since upgrading from MDT 2012 to MDT 2013.

I have not been successful adding any new model machines to the Lite Touch boot.  All our old existing hardware can boot into MDT 2013 as they did with MDT 2012, but when I tried adding new machines that required different network drivers, those would also boot to a command prompt and not even get to the TS selection page.

The sysprep and capture TS doesn't have that issue because you launch it from within Windows, but when it boots into Win PE, it has the same boot to command prompt problem.

The network appears to be working in this case because I can do ipconfig in the command prompt window after it fails and the vm has a valid dhcp address and can ping the mdt server.

• Edited by MyGposts 10 hours 37 minutes ago

This may be some kind of WinPE related issue because we have had second problem ever since upgrading from MDT 2012 to MDT 2013.

I have not been successful adding any new model machines to the Lite Touch boot.  All our old existing hardware can boot into MDT 2013 as they did with MDT 2012, but when I tried adding new machines that required different network drivers, those would also boot to a command prompt and not even get to the TS selection page.

The sysprep and capture TS doesn't have that issue because you launch it from within Windows, but when it boots into Win PE, it has the same boot to command prompt problem.

The network appears to be working in this case because I can do ipconfig in the command prompt window after it fails and the vm has a valid dhcp address and can ping the mdt server.

• Edited by MyGposts Friday, August 14, 2015 8:55 PM