Hello there,
I am planning to create a mobile SCCM server. My idea is, that I can ship this client to new company sites and help rollout the new clients and save bandwith. My question now is if someone already went through such a process or can give me an idea about what I have to think about, what is necessary and what problems I might get.  For instance I have no idea how I setup the Boundaries (I am now using the AD sites and services) but in a "mobile" scenario I see problems there.
I would appreciate ideas and help in this one.
Cheers Chris

Chris did you ever have any success with your idea?  I am new to sccm and thought the same thing.  i want to make my laptop a distribution point.

 

Thanks  Doug K

are you looking for BDP on laptop?

This can be achieved but there is a high possibility that you will end up in more complicated situation in the future.

That can basically be done, but requires some (troubleshooting) knowledge about ConfigMgr (especially when the shipping time is more than a few days, because you might run into replication issues that have to be fixed then). So it's not the best idea. Why not placing a secondary site (or whatever might fit best in that scenario) permanently to the remote location? The clients can then be managed after the rollout, too.

I've used Mobile DP on large customers 15000PCs lots of times who had many locations without servers. Even with Multicasting. Works like a charm.

Take a Laptop, with SSD disk, 2008 R2. Add it as a SCCM DP to that site.

 

Regards,

Nicolai

Nicolai,

Sorry to resurrect an older topic, but how would you approach such a thing?

If my company would want to integrate a new company, before any connectivity is made, would it be possible load Sccm unto a laptop, go to that location and distribute patches and AV with the help of Sccm?

It's possible, but not very fun. ConfigMgr uses a client agent so you'd have to load the client agent on all of their systems also. Nicolai's post above is specific to the DP role, not ConfigMgr as a whole.

Aquisitions are always a major pain point. If this is real-world for you today and all you need is updates, then WSUS would be my first option followed by InTune (depending on the org's size) if you need more immediate, short-term management.

It would be needed for Updates, deploying AV and deploying mandatory tools and then scan and document all computers both for hardware/software.

My thoughts currently would be to load a primary sccm server on a laptop, and then use the following MS document, http://social.technet.microsoft.com/wiki/contents/articles/3021.aspx for assist in this.

Can this be seen as a workable solution? Or better to put up a new Sccm server in that domain?

I'm not following your question: standing up a primary site is a new server. Without connectivity, a new primary site wouldn't be able to connect back to your current ConfigMgr hierarchy so there really is no difference. How are you going to manage this new site without connectivity?

I was thinking of 3 possible scenarios. All taking into account that no domain trust can be made untill all the computers are secure. Thanks already for the Intune tipe, I was unaware of this tool.

If there would be a wan connection between the 2 domains, a laptop with a preconfigured and loaded with all packages, secondary server that can be used then to distribute the client and updates,... which would also allow information to flow back to our head office.

If there is no wan connection, a laptop with a preconfigured and loaded with all packages,primary server so the settings can be configured then on the site.

Or settings up a new Sccm inside that domain, creating the packages for updates, AV and distribute them then. When everything is secure, and a domain join can be done, to connect that Sccm server to the current structure.

Am I looking at this in the correct way for a possible solution, or are there any obvious or non obvious technical burdens that would prevent this?

A couple of comments:

- ConfigMgr doesn't care about domains and trusts for managing clients.

- It is not supported to change the domain membership of a ConfigMgr site system

Based on the info provided, I would opt for a temporary ConfigMgr site on their network to manage their systems. You could initially make this system a child primary of your hierachy to replicate the content to it and then break the parent-child relationship for normal operation. If their domain is going away and connectivity will be established, you could then re-establish the parent-child relationship of the sites and move their clients to your primary site and retire the temp site. There are possible variations dpending on what happens with the domain and connectivity though.

Hello Nicolai,

Could you please assist with the steps required to setup Mobile Distribution Point.

We have requirement to perform OSD deployment in multiple locations.

Thanks,

Sushant

There's nothing to really set up, it's simple a DP that you physically move. The only thing you have to do is change the boundary group the DP is associated with when you actually move the server.