stgoodyeara Posted January 28, 2016 Posted January 28, 2016 Hi, Ive got a 3x Toshiba Sat Pro R50-B-12P laptops on 2 different sims sites. None will accept the solus3 agent. I gets as far as "copying agent files" then goes to Access denied to the remote computer. Ive checked: 1. The server can see the Laptops to rule out DNS issues 2. Disabled the Firewall on the laptops 3. Tried every user that could possibly have permissions 4. Creating new admin account, login to the laptop and then trying to push the agent. Any ideas?
JATSO Posted January 28, 2016 Posted January 28, 2016 Hi, Ive got a 3x Toshiba Sat Pro R50-B-12P laptops on 2 different sims sites. None will accept the solus3 agent. I gets as far as "copying agent files" then goes to Access denied to the remote computer. Ive checked: 1. The server can see the Laptops to rule out DNS issues 2. Disabled the Firewall on the laptops 3. Tried every user that could possibly have permissions 4. Creating new admin account, login to the laptop and then trying to push the agent. Any ideas? Have you added the firewall rules for solus and sims? Turning the firewall off isn't enough.
JATSO Posted January 28, 2016 Posted January 28, 2016 Hi, Ive got a 3x Toshiba Sat Pro R50-B-12P laptops on 2 different sims sites. None will accept the solus3 agent. I gets as far as "copying agent files" then goes to Access denied to the remote computer. Ive checked: 1. The server can see the Laptops to rule out DNS issues 2. Disabled the Firewall on the laptops 3. Tried every user that could possibly have permissions 4. Creating new admin account, login to the laptop and then trying to push the agent. Any ideas? Maybe this will help. What firewall exceptions does SOLUS 3 require to be input in Windows Firewall Configuring the Windows Firewall for SOLUS³ Agent Communication Workaround 1. Load the Group Policy Editor and navigate to the Windows Firewall node (http://technet.microsoft.com/en-us/library/bb490626.aspx). 2. Open the Windows Firewall: Define port exceptions properties dialog. IMPORTANT NOTE: Ensure that you access the Windows Firewall: Define port exceptions properties via the correct route. The correct route is Computer Configuration | Policies | Administrative Templates | Network | Network Connections | Windows Firewall | Domain Profile | Windows Firewall: Define inbound port exceptions. 3. Select the Enabled radio button. 4. In the Options panel, click the Show button to display the Show Contents dialog. 5. Add the following values: 52965:TCP:*:Enabled:SOLUS 3 Deployment Server 52966:TCP:*:Enabled:SOLUS 3 Agent 8739:TCP:*:Enabled:SOLUS 3 Agent Notifier UI IMPORTANT NOTE: Setting group policy port exceptions disables local port exceptions unless overridden in group policy. To do this, open the Windows Firewall: Allow local port exceptions properties dialog and select the Enabled radio button. 6. Click the OK button to close the Show Contents dialog. 7. Click the OK button to close the Windows Firewall: Define inbound port exceptions dialog. 8. Open the Windows Firewall: Allow inbound remote administration exception properties dialog. IMPORTANT NOTE: Ensure that you access the Windows Firewall: Allow inbound remote administration exception properties via the correct route. The correct route is Computer Configuration | Policies | Administrative Templates | Network | Network Connections | Windows Firewall | Domain Profile | Windows Firewall: Allow inbound remote administration exception. 9. Select the Enabled radio button. 10. In the Options panel, enter * in the Allow unsolicited incoming messages from these IP addresses: field. 11. Click the OK button to close the Windows Firewall: Allow inbound remote administration exception dialog. 12. Open the Windows Firewall: Define inbound program exceptions dialog. 13. In the Options panel, click the Show button to display the Show Contents dialog. 14. Enter: C:\Windows\System32\wbem\unsecapp.exe:Enabled:.NET Proxy for DCOM (WMI). 15. Click the OK button to close the Windows Firewall: Define inbound program exceptions dialog. Also, these ports need to be open on all devices: TCP 139, UDP 137, UPD 138 for browsing the network (NetBios) on all devices.
stgoodyeara Posted January 28, 2016 Author Posted January 28, 2016 Have you added the firewall rules for solus and sims? Turning the firewall off isn't enough. Surely OFF is exactly that off? Its strange how it seems to be the same model of laptop too. Ive got tones of other laptops that havent needed any further firewall work.
JATSO Posted January 28, 2016 Posted January 28, 2016 (edited) Surely OFF is exactly that off? Its strange how it seems to be the same model of laptop too. Ive got tones of other laptops that havent needed any further firewall work. I had to put those firewall rules in for every deployment, the rules can be exported and imported if it works. Also ensure your remote desktop connection is enabled for administrators. Edited January 28, 2016 by JATSO
stgoodyeara Posted January 28, 2016 Author Posted January 28, 2016 Ill try anything so ive just boshed them all in. ill let you know.
stgoodyeara Posted January 28, 2016 Author Posted January 28, 2016 Firewall changes dont work still saying same. The laptop has picked up the policy because i can see the listed entries in the firewall exceptions panel. It strange it looks as if its going to work, it goes to status install active and then onto checking operating system then onto checking framework versions, then onto copying agent files for afew seconds before it goes access denied. My gut feeling is that its finding the device but getting access denied at the point at which it want to write to the disk
matt40k Posted January 28, 2016 Posted January 28, 2016 Did you do a fresh install of Windows? Or is this the OEM build?
stgoodyeara Posted January 28, 2016 Author Posted January 28, 2016 OEM Build - - - Updated - - - Ive also tried exporting the installer and running it on the machines and then adding it to the console. Still end up at the same access denied place
stgoodyeara Posted February 1, 2016 Author Posted February 1, 2016 still struggling with this... anyone any other ideas? @matt40k what is the significance of the OEM vs Fresh Build?
matt40k Posted February 1, 2016 Posted February 1, 2016 To be honest, I would always recommend wiping and installing a clean copy of Windows. Toshiba builds are pretty clean, I've got a R50-B-12Q at home, still wiped it and started again. Sorry if this sounds pretty blunt, but I wouldn't bother spending time trying to fixing it (unless I'm getting paid by the hr) until its a fresh Windows install, joined to the domain, all the updates applied and connected correctly to the network - so same subnet, server can ping client dns name and the client and ping the server dns server. Remember SOLUS3 is two-way communication. Could have some random 3rd party antivirus that has a "firewall" option or it could be something else using the port. Ideally you would want only have 1 dns entry for laptop, so if the laptop is wired in, the wifi gets disabled.
stgoodyeara Posted February 1, 2016 Author Posted February 1, 2016 yeah this kind of rings true. I do have a couple of these models in question that i have clean built and they work fine. Tricky thing is getting them back in from the user to wipe em
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