Problems Deploying a Package.

[dustinlammers]

Hello,
Our company recently decided to go to a universal screen saver format with password protection being set after 7 minutes and the tab being complety hidden from the Display menu. I created an executible through SMS Installer to make the necessary registry changes. The problem is when I got to Advertise the package to clients, it always seems to fail upon running. My guess is that because the HKEY_CURRENT_USER is where most of the registry changes the user's cannot modify keys even though I select run with administrative rights. Any ideas? Tips? Solutions?

Thanks

Dustin.

 

[dustinlammers]

The error message looks like this:

"An error occurred while preparing to run the program for advertisement "SBC20028" ("ScreenSaver" - "Test Screen Saver&quot. The operating system reported error 2: The system cannot find the file specified. Additional program properties:
Command line: Screen Saver.EXE
Working directory: \\SMSSQL\SMSPKGF$\SBC00013Drive letter (? = any): UNC

Possible cause: This message most commonly occurs when the program’s command-line executable file could not be found, when a required drive letter connection to a distribution point could not be established, or when the program is configured to use the Windows NT Client Software Installation Account but the account is not specified, could not be found, or does not have the appropriate permissions.
Solution: Check each of the items listed above. "

Any ideas??

 

[jamagnus]

Hi,

I had trouble running command line packages until I set the program of the package to run with a drive letter (as oppased to UNC). I didn't specify a specific drive letter - just tell it it needs to run from a command prompt. I just couldn't get any command line (DOS-esque) packages to run until I set that in the package's program parameters.

JM

 

[dustinlammers]

Thanks for the tip I was able to get the package to advertise but I am having problems getting it to run properly on the users' PC's. It won't make the necessary changes to the registry, even though I am running it with administrative rights. Any ideas how to distribute a package that changes the registry while logged in as a non administrative user?? Any help would be greatly appreciated.

 

[maegirl75]

The HKEY_Current_User key will always be a problem because admins do not have access to it. Try pushing this package with User rights and only when the user is logged on. That's how I ran several packages that needed to access that reg key. And if all else fails, run it with Kix scripting via the logon script. That worked for my company.

 

[dustinlammers]

Thanks alot maegirl I will definitely give this a whirl ASAP.