Windows Thread, Cannot deploy any MSI's in Technical; Just as I thought I couldnt run into any more problems sorting out the new server, Ive found another
I ...
-
5th June 2008, 09:57 AM #1 Cannot deploy any MSI's
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
-
-
IDG Tech News
-
5th June 2008, 10:01 AM #2 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.
-
-
5th June 2008, 10:03 AM #3 I would make 100% sure that all your DNS ahost records are correct...
DNS is the root of al problems...
-
-
5th June 2008, 10:08 AM #4 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.
-
-
5th June 2008, 10:10 AM #5 
Originally Posted by
Singist
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.
-
-
5th June 2008, 10:10 AM #6 
Originally Posted by
Michael
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 
Old server died anyway so nothing could be moved
I will check DNS and add authenticated users
-
-
5th June 2008, 10:13 AM #7 On my share Everyone has full control. I usually deploy MSIs at machine level.
-
-
5th June 2008, 10:14 AM #8 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 \\<domain>\share rather than \\<server>\share. When you set up a new server you just put that server's name in the namespace and everything carries on.
-
-
5th June 2008, 10:19 AM #9 
Originally Posted by
Michael
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
-
-
5th June 2008, 10:20 AM #10
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.
-
-
5th June 2008, 10:24 AM #11 DNS was fine
But authenticated users were not there. Added them and Smartboard has just installed fine
. So cheers
Basic stuff I know, but brain is not working properly today
-
-
5th June 2008, 11:03 AM #12 
Originally Posted by
Michael
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.
-
-
5th June 2008, 11:04 AM #13 The everyone group includes all groups but does not contain the SID for Anonymous anymore.
-
SHARE: 
Similar Threads
-
By Newton in forum Windows
Replies: 10
Last Post: 25th April 2008, 11:40 AM
-
By contink in forum Windows
Replies: 6
Last Post: 15th January 2008, 08:30 PM
-
By Athlona in forum General Chat
Replies: 21
Last Post: 14th January 2008, 11:35 PM
-
By alonebfg in forum Windows
Replies: 12
Last Post: 7th November 2006, 09:19 AM
-
By ICTNUT in forum How do you do....it?
Replies: 16
Last Post: 4th July 2006, 04:09 PM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules