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



Reply via email to