I'd be interested in hearing other experience with continued management of XP 
too.  I told my folks that in order to continue managing XP I would need to 
stand up a parallel separate SCCM 2012 infrastructure along with the staff 
resources required to manage and maintain it.  Then they can make a business 
decision on whether they want to continue to be able to manage XP systems or 
not based on the cost to do so.   It would be helpful to have an informal list 
of what is broken and what still works with SMS CB and XP.

There is this post on user voice asking for a minimum of functionality for XP 
to be kept in SCCM 1511, and the response is that there is nothing in 
particular that is broken or disabled in XP - it is just all available with a 
caveat of "your mileage may vary"

https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/11171355-i-want-xp-server2003-lite-support-in-configmgr-151



From: [email protected] [mailto:[email protected]] On 
Behalf Of RJ Subscriber
Sent: Friday, April 15, 2016 1:19 PM
To: SCCM List
Subject: [mssms] SCCM 2012 1511 and XP Error Running Software Center


We still have some old XP SP3 systems due to manufacturing processes and have 
been using SCCM 2012 without issue until we upgraded to 1511.  The clients were 
upgraded through the automatic upgrade process.  The Software Center won't 
launch from the notification area, get "Access Denied" error.  It won't run 
from Start Programs either, getting error "Unable to open this Internet 
Shortcut.  The protocol "softwarecenter" does not have a registered program."



Tried full re-install of the client but no joy.  I can manually run 
scclient.exe and get the Software Center to come up, so I have a workaround.



I know XP is no longer supported but that's not the reality for manufacturing 
machines.



Thanks,

Russell



________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
may be legally privileged.  If you are not the intended recipient, you are 
hereby notified that any retention, dissemination, distribution, or copying of 
this communication is strictly prohibited.  Please reply to the sender that you 
have received the message in error, then delete it.  Thank you.
________________________________



Reply via email to