Seperate Server for OSD Deployment
I am currently fighting the good fight to get PXE enabled on our current SCCM Server. The push back I am getting is our server team is a bit worried that the IO to the server and traffic would be to great for it. Does anyone have any stats
on OSD Deployment or know a good way that i can prove that PXE and OSD Deployment in SCCM will work find on our current server. Also, is imaging on a seperate box going to take an install of SCCM on the server?"You can't fix stupid!"
July 22nd, 2011 2:01pm
using Windows Server's performance monitor, you can actually run some predifined data collection (using data sets)
here's some info about that from Technet
http://technet.microsoft.com/en-us/library/bb932169.aspx
you should probably focus on cpu load/disk activity and network load, all are included and you can customise the data gathering
they have their own forum right
here
if you are running server 2008 or higher, you can lessen the load by enabling Multicasting
cheers
niall
My step by step
SCCM Guides
I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
July 22nd, 2011 2:23pm
PXE in ConfigMgr only delivers the boot image. Nothing more. All content is still delivered from your DP(s) just like with boot media or adverts. So you're only adding a trivial amount of overhead: boot images are usually around 150MB.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
July 22nd, 2011 4:13pm


