SMS 2003 and SCCM annoyances
I am working on generating a list of DCR (Desired Configuration Requests). The following are some high level complaints
-
WQL. Simply why are we using this instead of SQL for console connections? I understand the need for WQL on a client because of the intense use of WMI. However, a client is pulling all the info directly from SQL. So why the WQL?
-
Lack of Multithreading. Almost every server now has multicore and multisocket CPUs. Why are so many threads in SMS linear? My biggest complaint is the collection evaluation SMS_Collection thread. If there are multiple collectionstatus at 5 why isn't the multicore cpus turning through those like butter?
-
DFS, Dynamic File systems. Why are DPs not put into a DFS. That way a traveling client will always attempt to connect to same share and have DFS determine cloesest. Talk about solving the source path healing issue if a DP/Share goes down with no product code available.
-
Powershell integration?
Just thinking out loud