![]() ![]() Because Configuration Manager 2007 assumes it has complete ownership of a logical drive when it uses naming conventions, site systems running on separate computers can’t share a logical partition on any storage technology, but they could each use their own logical partition on a physical partition of a shared storage device.įor more information about the use of System Area Networks and Configuration Manager 2007, see the following related Knowledge Base articles: Using a Storage Area Network (SAN) is supported as long as a supported Windows server is attached directly to the volume hosted by the SAN.Ĭonfiguration Manager 2007 is designed to work with any hardware that is certified on the Windows Hardware Compatibility List (HCL) for the version of the operating system that the Configuration Manager component is installed on.Ĭonfiguration Manager 2007 site server roles require NTFS file systems so that directory and file permissions can be set. There is a lot going on in the registry pointing to specific inbox paths etc., which to me puts into question whether the restore process would be intelligent enough to find the new installation path? The other option I'm thinking of is to use a swing box to act temporarily as a central site server - would this be do-able? Hardware availability may well rule out this option for us though. Would you expect significant performance benefits in this type of scenario if the SCCM installation is on SAN storage as opposed to a local mirrored set? This is a large installation with 200+ secondaries below each primary (however the central has no clients and only 5 primaries below it). Currently one of the primaries disk queue length is generally between 8 and 12. We had major disk queue length issues on our central, which led to this plan (however this has been mostly sorted out after fixing a DDR backlog issue). SQL is currently running on another server. The disk performance will be way better on the SAN - thus the thinking to move the whole SCCM installation. In fact on the packages front we already have them on the SAN for better performance, however the SCCM installation is on the C: drive (local storage in a mirrored set I believe). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |