locked
Install Client on one server to point at another RRS feed

  • Question

  • I have two SCCM 2012 servers which are on two separate networks and cannot see each other.

    I use one server to build the PC's and the other looks after them on the live network.

    The client however needs to be manually reinstalled every time I do this- is it possible to tell one server to install the client but make it point at the other server?

    Wednesday, April 22, 2015 4:08 PM

Answers

  • Assuming you are using OSD, no this is not possible directly within the task sequence.

    You could script it and kick it off with a post action though.

    What's the reason for these two different environments?


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


    Wednesday, April 22, 2015 4:40 PM
  • When installing the agent, the client needs to communicate with the site server, so no matter what you do this can't be done when the client is on the other network.

    However, like Jason says you can install/re-install/re-configure the client after you've moved the client to the new network.

    You might add a local start-up script to the client that will check if it can contact the new site server, and then re-install.

    If you join the client to a domain another solution could be to use a startup script using a GPO.


    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs: www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter @ronnipedersen

    • Marked as answer by Daniel JiSun Friday, May 8, 2015 2:29 AM
    Wednesday, April 22, 2015 5:20 PM

All replies

  • Assuming you are using OSD, no this is not possible directly within the task sequence.

    You could script it and kick it off with a post action though.

    What's the reason for these two different environments?


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


    Wednesday, April 22, 2015 4:40 PM
  • When installing the agent, the client needs to communicate with the site server, so no matter what you do this can't be done when the client is on the other network.

    However, like Jason says you can install/re-install/re-configure the client after you've moved the client to the new network.

    You might add a local start-up script to the client that will check if it can contact the new site server, and then re-install.

    If you join the client to a domain another solution could be to use a startup script using a GPO.


    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs: www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter @ronnipedersen

    • Marked as answer by Daniel JiSun Friday, May 8, 2015 2:29 AM
    Wednesday, April 22, 2015 5:20 PM