Hi,
Thanks you for the great tools, it really makes the life easier.
I've experienced an issue with Policies Manager.
The root-cause of the problem is probably not in the Policies Manager itself, but corrupted server/datastore/whatever...
This is transscript while using commnadline tool:
C:\Program Files\Citrix Tools\XenApp Policies Export Manager>XaPolMgrCmd.exe pol
icies export -dstfile:"c:\temp\mypol.xml" -polname:All
XenApp Policies Export Manager - By CitrixTools.Net - Version 1.0.4.0
Testing if On XenApp Server And If User is Citrix Admin ... OK
Farm : CitrixEMEA_XA5_T
Starting Export Job On 12/1/2009 5:21:08 PM
Processing Policy : Audio
Processing Policy : Default XenApp Policy
Processing Policy : Disable Client Printers
Processing Policy : Enable Client Printers
Processing Policy : TWAIN
Processing Policy : UPD
Export Ok
C:\Program Files\Citrix Tools\XenApp Policies Export Manager>XaPolMgrCmd.exe pol
icies import -srcfile:"c:\temp\mypol.xml" -polname:All -importfilters:Yes -Disab
leinit:No -overwrite:yes -username:XXXXXX\XXXXXXXXXX -password:XXXXXXXXX
3
XenApp Policies Export Manager - By CitrixTools.Net - Version 1.0.4.0
Entered UserName: XXXXXXX\XXXXXXXXXXXXX
Entered Password: XXXXXXXXXX
Testing if On XenApp Server And If User is Citrix Admin ... OK
Farm : CitrixEMEA_XA5_T
Starting Import Job On 12/1/2009 5:22:02 PM
Processing Policy : Audio
Processing Policy : Default XenApp Policy
Processing Policy : Disable Client Printers
Processing Policy : Enable Client Printers
Processing Policy : TWAIN
Processing Policy : UPD
Import Error
C:\Program Files\Citrix Tools\XenApp Policies Export Manager>
As you can Export works OK.
Import fails. (While on another computer it succeeds)
And this is actually turningpoint of the story. Import fails, but DELETION of the policies, which occurs before the eventual import succeeds.
The result is, that I end-up with NO policies. Which is quite uncomfortable situation.
So I wanted to ask, if there could be implemented some fail-safe check to avoid similar situations.
For example: The tool could try to import (and than delete) some fake policy (with the lowest priority) and based on the result decide if to proceed or not. (I can implemnet such check using my scripting framework on my farms. But having such feature by default can could safe the day to many people.)
Thanks
Lukas
P.S.: If debug mode is enabled, GUI returns following error:
---------------------------
XenApp Policies Export Manager
---------------------------
Message : Exception from HRESULT: 0x8004026A
Exception : System.Runtime.InteropServices.COMException (0x8004026A): Exception from HRESULT: 0x8004026A
at Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack)
at CitrixTools_XenApp_Utilities.XenAppLib.ImportPolicy(XmlDocument& objXML, XmlElement& objPoliciesList, String PolicyName, Boolean ImportFilters, Boolean DisableInit, Boolean OverwriteExistingPolicy)
---------------------------
OK
---------------------------