Jump to content


LoPHaT

Established Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by LoPHaT

  1. not sure if you would want to take this approach but I have done this in my lab many times...just shut down the existing SCCM server you have now clear out your System Management folder in AD and stand up another SCCM server. Setup the correct configurations for your environment and re-deploy the client to all systems, check the box to always install or re-install existing client. Once the new client is installed it will pick up the new MP.

     

     

    Nice! Thank you for the reply and info. It seems like a fairly straight forward process.

     

    Lo

  2. based on what you've said i'd suggest a side by side approach, boundaries will assist you here

     

    Thanks for the reply. May I bother you for a bit more of a step-by-step approach?

     

    Example:

     

    1. Bring up a Windows 2008 R2 machine

    2. Install SCCCM

    3. Install R3

    4.

    5.

    6.

     

    Brief guidance on best practices for setting up boundaries would be greatly appreciated. I don't want to jeapordize my current environment.

     

    Thank you!

  3. Greetings Anyweb,

     

    Great forums and resources here. Thank you for your time and effort sharing your knowledge and experiences.

     

    Here are my questions: I want replace my current setup with a new build of SCCM 2007 R3. I'm currently running SCCM 2007 SP2 for our organization (about 800+ machines). We have a nice VMware infrastructure and I want to rebuild the server there. What I need to know is how do I bring up another SCCM 2007 server without having it interfere with our current infrastructure? When the new VM environment is live, I want to be able to switch over and drop the other. I'm thinking I want to build the R3 virtual environment up and I was hoping I could just migrate the SQL database over from the previous instance, but with the new environment being R3 - will that jive?

     

    I perform image captures/deployments, WSUS updates/management, software deployments, etc. in my current environment... I look forward to your response.

     

    Lo

  4. I too have been searching for a solution to simply package the SCCM ConfigMgr Console so that I can deploy it to other admin machines for support-related needs... I have yet to find a simple way to accomplish this. Here is the most helpful I've found so far, but not as straight-forward as it should be:

     

    Deploy ConfigMgr Admin Console with MDT & R2

     

    Note that the link above also includes references to the Microsoft Deployment Toolkit (MDT). You can acquire the needed MDTs here.

     

     

    And for anyone else out there who's reading this thread, please post any helpful additions to this topic.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.