Tuesday, June 21, 2011 4:49 PM
Hello Everyone. I'm posting here because i think some of you could have some ideas about what can i do.
This is the case: I have an ISA Server but It lost its Configuration Storage. I can create a new configuration storage and it does not matter for me now.
The ISA Server continue working perfectly from his cached configuration, it continues working as a firewall and proxy, but due the configuration storage is not available i cannot manage it.
¿Do yo know how i can access to this cached configuration? I Need to save the policies and configurations.
Thank you for your help.
Ricardo Polo "HodracirK"
Tuesday, June 21, 2011 5:11 PM
Do you think that changeStorageServer.vbs could work?
Ricardo Polo "HodracirK"
Friday, June 24, 2011 2:15 AMModerator
Thank you for the post.
Please refer to this article: http://technet.microsoft.com/en-us/library/cc302686.aspx.
Problem: Neither primary nor secondary Configuration Storage servers are accessible. You want to specify an alternative Configuration Storage server.
Cause: The Configuration Agent can switch to another Configuration Storage server only by reading a configuration change from the currently configured Configuration Storage server, which is not available.
Solution: You can specify an alternate Configuration Storage server by using the ChangeStorageServer.vbs script, available in the FPC\Program Files\Microsoft ISA Server folder on the ISA Server CD. For script usage instructions, run:
cscript ChangeStorageServer.vbs ?
Nick Gu - MSFT
- Marked As Answer by Nick Gu - MSFTMicrosoft Contingent Staff, Moderator Monday, June 27, 2011 6:22 AM
Friday, July 27, 2012 10:23 AM
changeStorageServer.vbs alone will not work for your problem.
The following is for TMG, but should apply for ISA as well.
Outline of steps needed to retrieve and restore TMG configuration if no EMS backup is available
- Install new EMS, make sure it has the same service pack and patches as array nodes;
- Export current array configuration from array node's registry to XML using script with root.ConnectToLocalStorage;
- Create new enterprise config;
- Create new array with the same name and DNS name as before;
- Modify XML file which was exported from registry (add/remove/move needed XML elements);
- Import modified XML into new array;
- Make configuration consistent - recreate/move needed rules and objects (including enterprise-level ones), make sure that mission-critical rules have no unresolved object references and that configurations successfully backs up to XML file;
- Reestablish configuration synchronization - change array's UUID in EMS LDS, so that it is the same as current array UUID in nodes' registry and wait for configuration to sync.
I described the above steps in details in the article
Anton Shabunin, MCSE, MCITP EA, MCT