Jump to content

Recommended Posts

Posted

Just as I thought I couldnt run into any more problems sorting out the new server, Ive found another

 

I cant see to deploy any MSI, whatever it is. I initially spent ages with a net framework one wondering what was wrong with it, but now the same has happened when I try and deploy Smartboard software and Read And Write Gold.

 

Every time, in the event log I just get :The installtion source for this product is not available. Verify that the source exists and you can access it

 

Im assuming its a permissions issue? SYSTEM has full control on all the folders with the MSI's in, I thought that was all you needed?

 

All of them worked fine from the old server

Posted

I usually create a share called Distribution, specify permissons here, then move/copy MSIs into this folder or sub folders.

 

If the MSIs worked on the old server, am I right in presuming you've moved the share to this new server? If so, then the UNC path would be different: \\oldserver\distribution\ compared to \\newserver\distribution, hence the MSIs cannot be found. You'd have to remove each software policy, then re-create it pointing to the correct UNC path.

Posted

I would make 100% sure that all your DNS ahost records are correct...

 

DNS is the root of al problems...:eek:

Posted
Have you added Authenticated users to your permissions. I also create a folder called SoftwareInstalls. Sometimes there is an issue that if when you are adding a new package you dont go through network places to browse to the package you need (otherwise it tries the local path on the server), it can throw up that message. Usually adding authenticated users does the trick tho.
Posted
Have you added Authenticated users to your permissions. I also create a folder called SoftwareInstalls. Sometimes there is an issue that if when you are adding a new package you dont go through network places to browse to the package you need (otherwise it tries the local path on the server), it can throw up that message. Usually adding authenticated users does the trick tho.

 

If you have set it to install before a user logs in you need to add domain computers group right on the share and folder.

Posted
I usually create a share called Distribution, specify permissons here, then move/copy MSIs into this folder or sub folders.

 

If the MSIs worked on the old server, am I right in presuming you've moved the share to this new server? If so, then the UNC path would be different: \\oldserver\distribution\ compared to \\newserver\distribution, hence the MSIs cannot be found. You'd have to remove each software policy, then re-create it pointing to the correct UNC path.

 

lol nah, even Im not that dopey :p

Old server died anyway so nothing could be moved

 

I will check DNS and add authenticated users

Posted

You must have domain computers included in the permissions list ("authenticated users" effectively includes that) and you will get the "source not available" if you don't (it's a confusing message because the source is available, it's just not available to the account trying to use it!)

 

As Michael says, if you move stuff to a new server then it all fals to pieces. You can make this not happen if you use DFS from the start. You don't have to set up replicas, just create a namespace with your one server in it. You then deploy by pointing to \\\share rather than \\\share. When you set up a new server you just put that server's name in the namespace and everything carries on.

Posted
On my share Everyone has full control. I usually deploy MSIs at machine level.

 

Everyone only includes users not computers, that why a the domain computers group needs access

Posted
Everyone only includes users not computers, that why a the domain computers group needs access

 

But it works? :) I have this configuration at several sites.

Posted

DNS was fine

But authenticated users were not there. Added them and Smartboard has just installed fine :D. So cheers

 

Basic stuff I know, but brain is not working properly today :p

Posted
But it works? :) I have this configuration at several sites.

 

If you are installing software when a users login then it would but not if you where doing it when the computers was booting.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...