/build/static/layout/Breadcrumb_cap_w.png

Adobe Creative Suite 3 on Windows 7

Hi,

Out of curiosity, has anyone attempted to silently deploy Adobe CS3 on Windows 7?

When installing manually it just works fine. When performing the 'by now well known and documented' silent setup.exe method however, it fails and says in the log I run an unsupported OS.
I also found out that the setup.exe runs just fine in silent mode when running it in compatibility mode. This seems to be a succesful way for faking the setup so it passes the OS check.

Because SCCM is used here I made a script that to do the above:

Option Explicit

Dim objShell,objFSO

Set objShell = CreateObject("WScript.Shell")
Set objFSO = CreateObject("Scripting.FileSystemObject")


' Setting "Parent Folder Name" for locating setup.exe
strSourcePath = objFSO.GetParentFolderName(Wscript.ScriptFullName)


' Add compatibility mode key
objShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers\+", "" ,"REG_SZ"

Const HKEY_LOCAL_MACHINE = &H80000002

Dim lRC,sPath,objRegistry

Set objRegistry = GetObject("winmgmts://./root/default:StdRegProv")

sPath = "SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers"
lRC = objRegistry.SetStringValue(HKEY_LOCAL_MACHINE, sPath, strSourcePath & "\setup.exe", "WINXPSP2")


' Execute installation
objShell.Run strSourcePath & "\Setup.exe --mode=Silent --deploymentFile=" & strSourcePath & "\install.xml --skipProcessCheck=1", 0, True


The script works just fine, when running the script manually.

Now the bad part however. When SCCM deploys it and tries to run it under the SYSTEM account the setup.exe fails again, the logs saying my I don't meet the OS requirements. So it seems like the SYSTEM account doesn't support running compatibility mode.

Dead end, out of ideas.


Am I the only one running into this? Has anyone else tried it yet, failed or succeeded? Maybe some fresh ideas?



Regards,
Rowan

0 Comments   [ + ] Show comments

Answers (4)

Posted by: Rheuvel 14 years ago
Brown Belt
1
Hi,

I prefer not to install all the MSI files seperately because it's about 30 of them.


Anyways, I've found the solution:
Each payload of the major applications (Photoshop, Illustrator, etc...) has a file called something like AdobePhotoshop10nl_NL.proxy.xml in their payload folder. The only thing you have to do is simply remove this part somewhere at the bottom of the file:
<SystemRequirementsJSON>[

{"OS":{"Macintosh":{"Require":[{"Version":"10.4.8"}],"Exclude":[{"Version":"10.4.8"}]},"Windows":{"XP":{"Exclude":true,"Require":{"MinServicePack":"2","@servicePack64Bit":1
,"Need64Bit":"0"}},"Server2003":{"Exclude":true},"Vista":{"Require":true}}}
}
]</SystemRequirementsJSON>


So, no need for messing around with compatibility mode anymore :)
Posted by: Rheuvel 14 years ago
Brown Belt
1
It's pending for approval ;)
Posted by: MicrosoftBob 14 years ago
Blue Belt
0
Are you able to install the MSI files without using SETUP.EXE using the parameter ISSETUPDRIVEN=1?
Posted by: anonymous_9363 14 years ago
Red Belt
0
Excellent work. Could you write it up as a 'Note' and post it to the 'Package KB'?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ