I have created an application to run an vbscript to set the Office User Info. The script is based on this "Hey Scripting Guy"-Blog entry: http://blogs.technet.com/b/heyscriptingguy/archive/2005/07/13/how-can-i-change-the-user-information-in-microsoft-office.aspx.
The SCCM application has a script based deployment type and just calls the vbs-file. The detection rule is based on the registry path HKCU\Software\Microsoft\Office\Common\UserInfo\UserInitials and ...\UserName.
The installation is set to run as user, only when a user is logged on. It is my understanding that with this setting the installation process is running within the user context.
I also have configured a dependency for my Office 2010 SCCM application without automatic installation. The Office 2010 application is deployed to devices and is working as expected.
Then I deployed my "Office User Info"-SCCM application to a user collection.
When I'm logged in as an admin user the "Office User Info"-Application is deployed by SCCM without any problems. This works as expected.
When I'm logged in as an normal user account, the deployment does not work. I always get an error 1 in the SCCM Software Center.
In AppEnforce.log I can see that SCCM is trying to install:
Wrapped the vbscript within a CMD:
++++++ App enforcement completed (0 seconds) for App DT "Set Office User Info" [ScopeId_69A9909A-128E-4699-B2EE-AF2B63282EC9/DeploymentType_c012d9ab-f70d-4dcb-8c85-a55407d29fb8],
Revision: 4, User SID: S-1-5-21-873728476-183598923-581009308-9700] ++++++ AppEnforce 17.09.2012 17:07:34 2796 (0x0AEC)
+++ Starting Install enforcement for App DT "Set Office User Info" ApplicationDeliveryType - ScopeId_69A9909A-128E-4699-B2EE-AF2B63282EC9/DeploymentType_c012d9ab-f70d-4dcb-8c85-a55407d29fb8, Revision - 4, ContentPath - C:\Windows\ccmcache\37, Execution Context
- User AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
A user is logged on to the system. AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
Performing detection of app deployment type Set Office User Info(ScopeId_69A9909A-128E-4699-B2EE-AF2B63282EC9/DeploymentType_c012d9ab-f70d-4dcb-8c85-a55407d29fb8, revision 4) for user. AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
+++ Application not discovered. [AppDT Id: ScopeId_69A9909A-128E-4699-B2EE-AF2B63282EC9/DeploymentType_c012d9ab-f70d-4dcb-8c85-a55407d29fb8, Revision: 4] AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
App enforcement environment:
Context: User
Command line: "install_OfficeInfo.cmd"
Allow user interaction: Yes
UI mode: 1
User token: not null
Session Id: 2
Content path: C:\Windows\ccmcache\37
Working directory: AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
Prepared working directory: C:\Windows\ccmcache\37 AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
Prepared command line: "C:\Windows\ccmcache\37\install_OfficeInfo.cmd" AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
Executing Command line: "C:\Windows\ccmcache\37\install_OfficeInfo.cmd" with user context AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
Working directory C:\Windows\ccmcache\37 AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
Post install behavior is BasedOnExitCode AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
Waiting for process 2280 to finish. Timeout = 120 minutes. AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
Process 2280 terminated with exitcode: 1 AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
Looking for exit code 1 in exit codes table... AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
Unmatched exit code (1) is considered an execution failure. AppEnforce 17.09.2012 17:07:38 4952 (0x1358)
When I call the vbscript directly, I get an error message from Windows Script Host:
Windows Script Host. could not execute. (Access denied).
When I click OK, the message closes and I AppEnforce.log has the following output.
+++ Starting Install enforcement for App DT "Set Office User Info" ApplicationDeliveryType - ScopeId_69A9909A-128E-4699-B2EE-AF2B63282EC9/DeploymentType_c012d9ab-f70d-4dcb-8c85-a55407d29fb8,
Revision - 6, ContentPath - C:\Windows\ccmcache\3a, Execution Context - User AppEnforce 17.09.2012 17:13:23 3136 (0x0C40)
A user is logged on to the system. AppEnforce 17.09.2012 17:13:23 3136 (0x0C40)
Performing detection of app deployment type Set Office User Info(ScopeId_69A9909A-128E-4699-B2EE-AF2B63282EC9/DeploymentType_c012d9ab-f70d-4dcb-8c85-a55407d29fb8, revision 6) for user. AppEnforce 17.09.2012 17:13:23 3136 (0x0C40)
+++ Application not discovered. [AppDT Id: ScopeId_69A9909A-128E-4699-B2EE-AF2B63282EC9/DeploymentType_c012d9ab-f70d-4dcb-8c85-a55407d29fb8, Revision: 6] AppEnforce 17.09.2012 17:13:23 3136 (0x0C40)
App enforcement environment:
Context: User
Command line: "OfficeUserInfo.vbs"
Allow user interaction: Yes
UI mode: 1
User token: not null
Session Id: 1
Content path: C:\Windows\ccmcache\3a
Working directory: AppEnforce 17.09.2012 17:13:23 3136 (0x0C40)
Prepared working directory: C:\Windows\ccmcache\3a AppEnforce 17.09.2012 17:13:23 3136 (0x0C40)
Prepared command line: "C:\WINDOWS\System32\wscript.exe" "C:\Windows\ccmcache\3a\OfficeUserInfo.vbs" AppEnforce 17.09.2012 17:13:23 3136 (0x0C40)
Executing Command line: "C:\WINDOWS\System32\wscript.exe" "C:\Windows\ccmcache\3a\OfficeUserInfo.vbs" with user context AppEnforce 17.09.2012 17:13:23 3136 (0x0C40)
Working directory C:\Windows\ccmcache\3a AppEnforce 17.09.2012 17:13:23 3136 (0x0C40)
Post install behavior is BasedOnExitCode AppEnforce 17.09.2012 17:13:23 3136 (0x0C40)
Waiting for process 4188 to finish. Timeout = 15 minutes. AppEnforce 17.09.2012 17:13:23 3136 (0x0C40)
Process 4188 terminated with exitcode: 1 AppEnforce 17.09.2012 17:21:31 3136 (0x0C40)
Looking for exit code 1 in exit codes table... AppEnforce 17.09.2012 17:21:31 3136 (0x0C40)
Unmatched exit code (1) is considered an execution failure. AppEnforce 17.09.2012 17:21:31 3136 (0x0C40)
I first thought that I do not have access as a user to the source directory within the ccmcache folder. But if I open a cmd, cd to the correct ccmcache subfolder (ccmcache itself is not accessible for users) I can dir the content and start the vbscript and or the wrapping batch file without problems.
I tried several thinks but I do not get this up and running.