I gave up on using SMPs ages ago after reading the post on Chris Nackers' blog (http://www.chrisnackers.com/category/9507/) and have never looked back. I recommend you take a look at it.
Thanks, ________________________________ Mark Mears [email protected]<mailto:[email protected]%0d> Phone: (757) 945-2651 [cid:[email protected]]<http://www.cireson.com/> [cid:[email protected]]<http://twitter.com/teamcireson> Check out our System Center App Store: www.cireson.com/app-store ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Thursday, November 14, 2013 10:37 AM To: [email protected] Subject: [mssms] Troubleshooting SMPs Hello folks I am fast becoming an un-fan of Microsoft's State Migration Points So, I have a system which I have completely backed out from being a site system. It's Server 2008R2. I deploy File Services & Web Services, using the default installation and then adding ISAPI etc. I then add the system as a site server. We are using 2012 SP1 no CUs I then deploy SMP role to it and the installation appears to go OK, no errors, component manager does its stuff etc. and reports that there is plenty of disk space. I leave it for several hours, just in case and then I mark an existing SMP as Restore Only Now when clients Request a State Store the only store that they are offered is the original server and not the new SMP - ever, regardless as to whether then have EVER run SCANSTATE I am now at a loss to understand why an SMP would not appear in the list delivered to the client - I assume that the MP drops this information down? Anyone got clues to help diagnose please? Jason
<<inline: image005.png>>
<<inline: image006.jpg>>
