squeeky Posted September 19, 2012 Posted September 19, 2012 Hi, Im trying to push out smart notebook 11 on to the network so that it installs automatically on newly deployed pcs. I have created my mst on Smart Install Manager and then saved it to the network share with my msi file that I have obtained from smart. However whne I apply it in the group policy (with the modifier) and then reboot a client smart essentials flashes past in about 15 seconds or so and doesnt install. The error i from eventvwr on client is far from helpfull: Log Name: System Source: Application Management Group Policy Date: 19/09/2012 15:04:55 Event ID: 102 Task Category: None Level: Error Keywords: Classic User: SYSTEM Computer: TEST-INSTALL Description: The install of application SMART Education Software 2012 from policy New-Clients failed. The error was : %%1612 Can anyone help with this because that error code turned up nothing for me except that the network source is not accessible. When I login I can access that network share so I assume it is ok ? Thanks Squeekymouse89
localzuk Posted September 19, 2012 Posted September 19, 2012 The error is an msiexec error - List of Error Codes and Error Messages for Windows Installer Processes in Office 2000 products Namely, the source can't be accessed. This is normally down to permissions. For deployments, I have a share with 'everyone' having read only access on both NTFS and share permissions. It seems to do the job fine.
SHimmer45 Posted September 19, 2012 Posted September 19, 2012 for the deployment share i add the domain computers share as in the guide i read about deployment its specified that this specific group be added to access the folder where MSI is shared from.
squeeky Posted September 20, 2012 Author Posted September 20, 2012 Hmm doesnt seem to make any difference i have everyone full access. Might it be because Ive used an ip not a dns name ? eg \\192.168.0.1\software\Smart\setup.msi obviously this isnt best practice but should still work
squeeky Posted September 20, 2012 Author Posted September 20, 2012 ahh ok for future reference and for others just make sure your MST file is still using the network path because on my server it had defaulted to local browsing and then was failing because it couldnt find the specified mst file
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now