/build/static/layout/Breadcrumb_cap_w.png

Samsung Kies silent installation

Hello peeps..

I really need some help with the silent installation of Kies, it has a commandline for a silent installation:

Kies_2.0.3.11082_152_4.exe /S

So, that should be it, in a administratoruseraccount it works perfect, the only problem is we deploy our software through the rootadminaccount, which has no userprofilesfolder, so when we try to install it, it won't work because it needs a profile to install.

So I managed to get the main MSI-file file, when starting setup it extracts to the following files:

Samsung kies.msi
1033.mst
0x0409.ini

The problem is i can't get this to work with the following commandline:

msiexec /a "Samsung Kies.msi" TRANSFORMS 1033.mst /qb

I even got so far to extract the main msi further into the following folders and files:

AppDataFolder
CommonAppDataFolder
ProgramFilesFolder
SystemFolder
TempFolder
WindowsFolder
kies.msi

But still I miss all the actions for the registry and links, has somebody experience with this package and please help?

Hope to hear from you all

Greetzz

0 Comments   [ + ] Show comments

Answers (14)

Posted by: KnyazA 12 years ago
White Belt
1

Hi all. To fix this problem on x64 should be used parameter /b, which change "CacheFolder" for InstallShield. I use following command line:

@copy SamsungKies2.3.0.mst %temp%\SamsungKies2.3.0.mst /y


@start /w Kies_2.3.0.12035_16_4.exe /b"%temp%" /s /v"transforms=%temp%\SamsungKies2.3.0.mst"

Posted by: ZaxXxaR 12 years ago
Yellow Belt
1
sure, no problem.

The root of error is as described, systemprofile. We've encountered this as well:
when as admin - is as charm, but when ie through psexec, you'll get this:


Steps to workaround:
1. Launch psexec -s -i cmd.exe
2. execute KiesSetup.exe /v"/l*v C:\temp\log.txt" - you'll get msi log.
3. search in log on first rows:
MSI (c) (94:DC) [12:51:49:400]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Windows\system32\config\systemprofile\AppData\Local\Downloaded Installations\{30C6A000-EB91-4747-B2CA-878514184621}\Samsung Kies.msi' against software restriction policy
- so you now know where it looks for!

4. Goto your system %TEMP%, usually C:\windows\temp
5. Find {GUID} folder with Kies.
6. Copy folder to mentioned above C:\Windows\system32\config\systemprofile\AppData\Local\Downloaded Installations\{30C6A000-EB91-4747-B2CA-878514184621}
7. execute installer. Do not use extracted MSI - it installs s*it without assemblies! Make transform and use smth like:
KiesSetup.exe /s /v"TRANSFORMS=C:\temp\KiesTransform.mst /qn"
...
PROFIT!:)


We are using this as batch:
- Copy files to temp
- Copy files to system profile
- launch setup silent
- clean files
Posted by: Steamofterror 12 years ago
Yellow Belt
1
Wow man!!! This helps a lot, i've got it almost working, if I put the files into C:\Windows\system32\config\systemprofile\AppData\Local\Downloaded Installations\{30C6A000-EB91-4747-B2CA-878514184621} and then run the setup, the package gets installed. The only problem we are facing is the copy action to C:\Windows\system32\config\systemprofile\AppData\Local\Downloaded Installations\{30C6A000-EB91-4747-B2CA-878514184621}

It gives a access denied back, our batch does the following:

mkdir "C:\Windows\System32\config\systemprofile\AppData\Local\Downloaded Installations"

mkdir "C:\Windows\System32\config\systemprofile\AppData\Local\Downloaded Installations\{30C6A000-EB91-4747-B2CA-878514184621}"

copy "%1\dist\{30C6A000-EB91-4747-B2CA-878514184621}" "C:\Windows\System32\config\systemprofile\AppData\Local\Downloaded Installations\{30C6A000-EB91-4747-B2CA-878514184621}"

%1\dist\Kies_2.1.0.11095_121_6.exe /S /v/qn

Does someone know how I can copy the files within the systemfolder as specified above?
Posted by: ZaxXxaR 12 years ago
Yellow Belt
1
If you are running as elevated admin/system - you should have enough rights.
...The only idea which comes to my mind is that you're copying from network source so WFP may reject it, maybe?

In my batch it's pretty much the same, but I do copy sources locally from distribution point:

@echo ================================================================================================
@echo *** Install of Samsung Kies
@echo *** 1. Copying source-files
SET SourceDir=%~dp0
MD %SystemDrive%\TEMP
XCOPY /S/E/Y/V "%SourceDir%*.*" "%SystemDrive%\TEMP\*.*"
XCOPY /S/E/Y/V "%SystemDrive%\TEMP\SYSTEM\*.*" "%windir%\system32\config\systemprofile\AppData\Local\Downloaded Installations\{30C6A000-EB91-4747-B2CA-878514184621}\*.*"


Check to be sure that you're executing in x64 cmd.exe context, otherwise it may search/copy to C:\Windows\syswow64 instead of C:\Windows\system32 if it's relevant for your target Clients.

P.S.: BTW, you still have uninstall.:)
It's simple, just modify with your guid:
@echo *** 2. Running Setup with parameters
taskkill /f /im KiesTrayAgent.exe /t
taskkill /f /im KiesPDLR.exe /t
CALL "%ProgramFiles(x86)%\Samsung\USB Drivers\Uninstall.exe" -s
CALL "%ProgramFiles(x86)%\InstallShield Installation Information\{758C8301-2696-4855-AF45-534B1200980A}\setup.exe" -runfromtemp -l0x0409 -removeonly -s -v"/qn"
Posted by: mindless 13 years ago
Yellow Belt
0
msiexec /a "Samsung Kies.msi" TRANSFORMS 1033.mst /qb
Try with: msiexec /a "Samsung Kies.msi" TRANSFORMS=1033.mst /qb
Posted by: Steamofterror 13 years ago
Yellow Belt
0
Sorry for the mistype, I did it as mindless says:

msiexec /a "Samsung Kies.msi" TRANSFORMS=1033.mst /qb

It does not work...:(
Posted by: Steamofterror 13 years ago
Yellow Belt
0
can someone help please?
Posted by: Steamofterror 12 years ago
Yellow Belt
0
Tjeez...almost there.....it does indeed copy it to syswow64, even with this in the script:


XCOPY /S/E/Y/V "%1\dist\{30C6A000-EB91-4747-B2CA-878514184621}\*.*" "c:\windows\system32\config\systemprofile\AppData\Local\Downloaded Installations\{30C6A000-EB91-4747-B2CA-878514184621}\*.*"

Is there anyway to execute this in x64 context or is it possible to give the setup the proper location?
Posted by: ZaxXxaR 12 years ago
Yellow Belt
0
yup, no problem.
You just following exactly my path right now and the same troubles.:)

Our deployment system allows to switch context, but that's not an option to you, as I understood?

In this case you could do it hard way:
1. Go to \system32 on x64 Client.
2. Copy cmd.exe from there. (Sending Rays of Love to MS here, but yes, you only need x64 cmd.exe)
3. Paste this cmd.exe to your distribution source.
4. Execute your script from that cmd.exe. In your case smth like:
"%1\dist\cmd.exe /c %1\dist\install.cmd"
where install.cmd is your batch with kies routines, including copying.
Posted by: Steamofterror 12 years ago
Yellow Belt
0
this is really something.....I did exactly what you described, I even copied the cmd.exe from a xp-machine....but still the same result....it copies to syswow64...:(((....
Posted by: mahendraKumar 12 years ago
Senior Yellow Belt
0
Hi Steamofterror,

this is possible since your MSI actions runs in 32 bit mode. Try to change the custom actions to 64-bit mode then your script environmental variables point to 64-bit locations.
Posted by: Steamofterror 12 years ago
Yellow Belt
0
a great idea, but still how to do that? Because the msi is run from within the setup which i can't modify...any ideas?
Posted by: mahendraKumar 12 years ago
Senior Yellow Belt
0
You can check if provided setup file is compatible with 64 bit then would be better solution.

since ,If it is Vbscript custom action u will find the "use 64bit Scripting" option enabled.
Rest of the custom action does not support this,so it is disabled by default.
Posted by: Steamofterror 12 years ago
Yellow Belt
0
Fixed!!!!! It was a search, but its quite easy, instead of copying to system32 folder, you should copy to sysNative folder, ZaxXxaR many thanks to you, you helped me alot!!!!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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