locked
Multiple Client Push Accounts, Only one account being used...? RRS feed

  • Question

  • We have a multi-domain environment with multiple client push accounts. 

    1 per domain for servers
    1 per domain for client

    all 4 accounts are listed in the client push settings

    The only account I ever see in the CCM log on the server is the following. domain1\JWCMSP. That client account does not have access to the clients i am attempting to install on only the domain1\JWCMCP account does... why does it never try the other accounts in my list? This same problem happens in both domains. 


    • Edited by I_Know_God Thursday, October 20, 2016 4:17 PM Title Change
    Thursday, October 20, 2016 4:09 PM

All replies

  • For the snippet above, it's because the account is not the failure, the machine is not reachable so the account is irrelevant. The second line in that screenshot tells with this explicitly so trying additional accounts makes no sense.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, October 20, 2016 5:41 PM
  • For the snippet above, it's because the account is not the failure, the machine is not reachable so the account is irrelevant. The second line in that screenshot tells with this explicitly so trying additional accounts makes no sense.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Doesnt it say access denied or invalid network path. meaning it could be ether one? it says that about every client even ones that clearly are reachable. 


    • Edited by I_Know_God Thursday, October 20, 2016 6:11 PM updated images
    Thursday, October 20, 2016 6:08 PM
  • Yes, it says that but you are focusing on the incorrect line -- you can't take a single line out of context. You need to read all of the info and digest it together.

    As I pointed out, the second line of your first screenshot explicitly says "does not exist on network, Giving up." Also, the error code, 35 (hex), means "The network path was not found."


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, October 20, 2016 6:14 PM
  • alright. Well firewalls are off. machines are on the same subnet, and servers that have the JWCMSP account in server admins work without an issue. 

    If i make the JWCMSP account a DA the clients install without issue. 

    So your saying it cant find the computer so it never checks the next account? what should my next options be. 

    Thursday, October 20, 2016 7:06 PM
  • Figure out why it can't reach that specific system. Normal connectivity troubleshooting from the site server. If could be all kinds of things including the system simply not be on, DNS messed up, a network firewall, a network filter, etc., etc.

    The two screenshots above are for two different systems so just because it worked on another system doesn't mean it will work on every system.

    Using DA is bad practice -- I'm sure you probably did it just for testing but in both cases above it has nothing to do with the account whatsoever.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Ant_G Thursday, November 3, 2016 9:34 AM
    Thursday, October 20, 2016 8:01 PM
  • Figure out why it can't reach that specific system. Normal connectivity troubleshooting from the site server. If could be all kinds of things including the system simply not be on, DNS messed up, a network firewall, a network filter, etc., etc.

    The two screenshots above are for two different systems so just because it worked on another system doesn't mean it will work on every system.

    Using DA is bad practice -- I'm sure you probably did it just for testing but in both cases above it has nothing to do with the account whatsoever.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    yeah I used two different computers to show that it wasnt related to that specific computer. After quite a bit of troubleshooting on this specific issue, I was able to pin down that VM's didnt have this problems only physicals. Then I was able to narrow it further by saying only notebooks, then only notebooks with wireless enabled, then finally only the wireless connection. 

    After looking at our wireless config on the WAP side we had a ACL that prevented all but certain ports to our devices by the wireless IP. This cleared up quite a bit of the issues and i saw the majority of the installs go through after this. 

    The installed checked multiple Client Push accounts as well. 

    I am not marking as complete quite yet as my child-domain clients haven't been installed quite yet so im still looking into it. I will however update and mark answer once the reason is found. 


    • Edited by I_Know_God Friday, October 21, 2016 3:54 PM Spelling
    Friday, October 21, 2016 2:25 PM