I have been recently using an exchange virtual lab on technet to configure an edge transport server using EMS. When I enter the command new-edgesubscription -file "c:\edgesubscriptionexport.xml" an error is generated "new-edge subscription : unable to load local keys in hub transport server"Does anybody know what this is?Thanks

Hi, I do not find any information regarding the error in our internal database. Would you please let me know whether you run the command on Edge server to create edgesubscriptionexport.xml file or run on the Hub Server to import edgesubscriptionexport.xml file? Whether is there any related event in event log? In addition, I also suggest you run ExBPA to check whether there are any related issues. ~~~~~~~~~~~~~~~~ Mike Shen TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com ~~~~~~~~~~~~~~~~

Hi MikeI had the same error. While doing the Step of the Exchange 2007 SP1 virtual lab, I switched to EDGE01 then opened Exchange Management Shell - MSH and typed: NEW-EdgeSubscription –file “c:\EdgeSubscriptionExport.xml”Any idea?

Hi, Whether do you also encounter the error when performing test on Technet Virtual Lab? I have local tested on following Virtual Lab, I am not able to reproduce your issue.http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032340485&EventCategory=3&culture=en-US&CountryCode=USIf you use other Technet Virtual lab, please send the link to me for local test.Thanks,Mike

Hi All,I am getting the same error message when trying to complete above technet virtual lab.Hope we can have it resolved soon.Thanks,Fadi

FadiSydney or anyone else, I'm having the same issue on the TechNet lab (Configuring an Exchange 2007 Edge Server). After running NEW-EdgeSubscription –file “c:\EdgeSubscriptionExport.xml” I get: NewEdgeSubscription : unable to load local keys in Hub Transport Server At Line:1 char:21 We're going to be putting in an Edge server soon, so it would be great to be able to complete the lab - any ideas, or is this lab just 'broken'? Thanks

There is definitely something wrong with this specific lab, I am getting the same error. Rebooting the machines did not work. How about getting your labs straight, MS?Erik Nettekoven | MCSE 2000 | MCSE 2003 | MCITP: EA