Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-18-2014 10:32 PM
Before you can use the deployment it seems you need provide a
Default Package Share username and password under the Security Options TAB.
I only see the info "Provide an account with read-execute rights only on the shared folder. Using an administrator account is a severe security risk! This password will be accesible to all users."
So, should his be a domain user? Must I make a new special domain user that can access this share? I'll then need to restrict it down so it can't access anything else or logon anywhere so will this affect it's use?
Where exactly is this user used in the sysytem?
Default Package Share username and password under the Security Options TAB.
I only see the info "Provide an account with read-execute rights only on the shared folder. Using an administrator account is a severe security risk! This password will be accesible to all users."
So, should his be a domain user? Must I make a new special domain user that can access this share? I'll then need to restrict it down so it can't access anything else or logon anywhere so will this affect it's use?
Where exactly is this user used in the sysytem?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-19-2014 09:10 AM
The easiest way would be to create a new domain user which has only access to this share.
This username is used each time a client deployment needs access to {packetshare} on the workstation.
This username is used each time a client deployment needs access to {packetshare} on the workstation.
13 REPLIES 13

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-21-2014 11:01 AM
The package share account is only used to access files on the packageshare, not for any scanning or deployment.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-20-2014 04:57 PM
Is this seperate from the permission the packages will run as? (ie system...logged on user..etc).
ie, is this really just for the remote system to be able to access any needed sources?
So basically a domain user that cant login to any pc would function?
ie, is this really just for the remote system to be able to access any needed sources?
So basically a domain user that cant login to any pc would function?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-19-2014 09:37 AM
Hello,
I already had an test account for testing policies in the our company. I used that tast account (Domain User) for the share.
With that credentials, my teamviewer quick support deployment works great!
Hope this helps.
Jordi Koller
A happy lansweeper user.
I already had an test account for testing policies in the our company. I used that tast account (Domain User) for the share.
With that credentials, my teamviewer quick support deployment works great!
Hope this helps.
Jordi Koller
A happy lansweeper user.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-19-2014 09:10 AM
The easiest way would be to create a new domain user which has only access to this share.
This username is used each time a client deployment needs access to {packetshare} on the workstation.
This username is used each time a client deployment needs access to {packetshare} on the workstation.
