I finally have SCMDM 2008 working in a VM environment, and I am getting ready to request hardware for a proof of concept. I was wondering if anyone knows why Microsoft recommends 100GB of disk space on EN, DM, and GW servers? That seems like a lot of overkill, unless there is a ton of logging. I understand that the databases could grow with the number of devices, but otherwise I do not see where this space would be needed.
It is overkill since you're only looking at the OS and executables plus log files. The SQL databases have the potential to get somewhat large but are the only component for which capacity is important.
For the MDM Infrastructure go with what you're comfortable with. That 100Gb number came from the need to have some kind of conservative guideline (note: guideline) and roughly splitting the difference between the prevelent manufacturer-provided 72Gb and 144Gb drives.
HTH.
best, Pat.Mobility Architect, Enterprise Mobile
Marked As Answer byKevin M PhillipsWednesday, July 23, 2008 6:09 PM
Moving along with my implementation, and I am trying to spec out the LUN sizing for the databases. Does MS have a DB sizing tool for planning SCMDM? Looking for up to 1000 mobile devices with lots of application package deployments.
Not that I'm aware of. Martin or one of the other MS guys who frequent this list would certainly know if there's anything available or in the pipeline.
You're not going to be looking at a very large database at all - bear in mind what it's storing is mainly inventory and history information from which the Reporting tools trigger.
As a very cludgy way of working it out, take the DB size with a known quantity of managed devices (say 10), leave it in this known state for a few days while pushing down policies, .cabs etc and then check the DB size. Extrapolate out by 100 and you're going to have a pretty good idea of what the minimum DB size will be and then apply SQL best practise for figuring out what the optimal LUN size would be. Sure, the DB will grow over time, but not much.
Not even close to being scientific, but that's just a suggestion straight off the top of my head!
All the .cab files you create for pushing down will reside on the WSUS server, so that's what you'd need to pay closer attention to. Even with WSUS co-located with the DM (which, as the earlier thread indicates would have around 90+Gb free space on it) you'd need to put a boatload of files out there before capacity were to become a concern.
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.
SCMDM 2008 System Requirements
.png)
