Machine-Assigned Applications

Machine-Assigned Applications

• 
  Is the machine account in the correct organizational unit?
  
• 
  Is the application deployed to users by mistake?
  
• 
  Was the machine rebooted since the deployment?
  
• 
  Does the machine account have access to the install point? The access to the install point is done via the machine account. See below for an example of how to check this using the "at" command.
  

• 
  Using a deployment server running Windows NT Server 4.0. Deploying a package from a share on a Windows NT 4.0-based server is not supported.
  
• 
  Deployment path as an IP address.
  
• 
  Deployment path in the format of \\domainname\share. You must use a machine name, not a domain name, in the path to the deployment share.
  
• 
  Deployment server is in a different Active Directory forest. The share from which a package is deployed must be in the same forest as the machine account that the policy will apply to.
  
• 
  The local system account does not have access to the deployment share.
  

1. 
   Use the AT command to open a command prompt running as the local system account. For example, if it is currently 9:52 P.M. you could run the following command: “AT 9:53p /interactive "cmd.exe.“
   
2. 
   From the command prompt that was started, attempt to access the package location by performing a dir command on the share. For example, run dir \\server\deploymentshare to attempt to list the contents of the share. If this command fails, you may need to change the permissions on the share to allow the system account access.