Brigg Angus
Comments
-
Hi Ndmoon, This can be a frustrating issue since lync.exe, which is both standalone Lync and Skype for Business, can be installed in different locations and in different directories depending on th...
-
Official comment
Hi Dan, This should work for you: All----Not Any------Application Name Equals Program1----All------Application Name Equals Program2 The same would work for the Application version, though you could...
-
Okay. To recap all the right things:1. You can ping the machine2. The machine name and IP match as expected for NetBT resolution3. DNS resolution works4. Firewall is allowing the necessary ports5. ...
-
This is a bit odd, I'll admit. Everything appears to be working as it should, and the magic should happen. Maybe something basic is amiss. Can you ping the target from the PDQ console machine?
-
There are a few other things we can check as well: 1. Would you click on one of the offending machines and then click on Inventory Help > Open Remote Repair and analyze the machine? What errors, if...
-
Hi Terry, Were you able to install .NET 4.5.2 or 4.6+, patch and then run Deploy or are you still getting the error? If you are, you will need to completely uninstall .NET and reinstall (a repair w...
-
Hi Lars, Were you able to run your O365 install command as a batch file locally on the machine using UNC paths and have it install correctly like Ben? Also, when you run the deployment as Deploy Us...
-
Thanks for letting us know about this Colby.
-
It is. In Free mode, you can create Active Directory collections, but there is no option to sync with Active Directory. This limitation doesn't apply to DNS hostname resolution, which applies at al...
-
It would only appear if it's either part of Active Directory and you have Active Directory Sync enabled and/or if the computer has a resolvable hostname in DNS.