If only it were that easy. The second SMP simply is not being delivered to the client at all.
From: [email protected] [mailto:[email protected]] On Behalf Of Chris Nackers Sent: 14 November 2013 22:08 To: [email protected]; [email protected] Subject: RE: [mssms] Troubleshooting SMPs You have an association in place and the data has been captured up to the new SMP? Chris Nackers Microsoft MVP - Enterprise Client Management Email: [email protected] Nackers Consulting Services, LLC From: [email protected] [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Thursday, November 14, 2013 9: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
