Deployment Solution

Hi,

I want run script with Dagent on Windows 7 like CMD /K

On Windows XP, I see a black cmd window with aclient

But on Windows Seven, I don't see this black windows.

I need to interract with desktop for other script.

How, I can use job for see this cmd windows.

I try to enable "Allow Service to interact with desktop" on "Altiris Deployment Agent" service.

This feature doesn't resolve this issue.

Do you have any idea ?

Thanks for your help,
Best regards,
Charlly

On the 2nd screen of the Run Script dialog, try selecting "Run script in console user session" instead of "Default (local system account)"

You indicated both SP1 and SP4 in your subject line.  We had several random issues with Windows 7 on SP3 but those went away with the update to SP4.  If you aren't running SP4 I'd recommend upgrading your DS.

Hi,

thanks,

If you use "Run script in console user session", you have user rights, I think.

But, I want Admin right (or System)

I upgrade to 6.9 SP4 and I have the same problem.

With this batch file:

cmd /k

Or with this vbscript:

'Vbscript
Msgbox "test"

Thanks for your help,
Best Regards,
Charly

Enable the administrator account, and run it as administrator?

That's because of the security architecture of Vista & Win7.

"run in console session" is the only way to do it.

Or log in as user "xy" on the client and configure the job to run with credentials of user "xy".

I've resolved creating an event that runs in "Console user session",

using followings parameters:

REM Execute command in user comnsole mode

\\%DSSERVER%\eXpress\DSLib\Local\Apps\Pstools\psexec.exe -i -s cmd /accepteula

-i  Run the program so that it interacts with the desktop of
    specified session on the remote system. If no session is
    specified the process runs in the console session. 

-s execute the command with the "nt authority\system" system account.

 

You can test It, starting the Task Manager and confirm the user that executed the command prompt.

 

regrads,

 

Michele F.

We had the same problem, this was resolved as below.

When we installed Altiris 6.9 SP4 we created and used a domain level service account (Altiris Service)

All of our images and desktop clients have the (Altiris Service) account in their local administrator group.

The (Altiris Service) account also has the appropriate access levels to all installation and image sources.

Because we are a multi site topology, allowing files to be copied using the Deployment server is extremely low, so we have configured all jobs to or "Copy Directly from source then Execute" and used the altiris service account credentials.

This has the effect on Windows 7 of executing the applicaiton install (or any other task) in the context of the Altiris Service Account user ID. thus it will have local administrative rights on the target machine.

I can then log in tot he client machine using hte Altiris Service account, and any windows will be avaliable, including desktop interaction requests.

This is kind of a wierd thing to do, but I found you can run explorer.exe a 2nd time in the hidden 'session 0' screen, if you want to see something in the taskbar at the bottom.  You should probably kill it when you're done.