Hi all, I installed SCCM with no problem on a SCVMM Virtual Machine running Windows 2003 std SP2. I configure Operating system deployment. When i try to make a Computer Association to Import Computer Infromation and import single computer using MAC Address i've get this error message: Error: Following computers have not been imported:Name: asdMAC Address: 00.A0.D1.A2.25.9FSMBIOS GUID: Source Computer: Choose Target Collection: None ChosenErrorsThe ConfigMgr Provider reported an error.ConfigMgr Error Object:instance of SMS_ExtendedStatus{Description = "No valid GUID or MAC";ErrorCode = 2152205056;File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspsite.cpp";Line = 1102;Operation = "ExecMethod";ParameterInfo = "SMS_Site";ProviderName = "WinMgmt";StatusCode = 2147749889;};I've tried lots of different MAC Address with the same result. Someone can help me? Thanks

Hi Tiziano, It looks like you are using periods . as seperators in your MAC address instead of colons :. What happens if you try 00:A0:C1:A2:25:9F ? -- Brett

Interesting. Thanks for your answer Brett. I used Import Computer Information wizard to import the MAC Address and the mask of the wizard was without separators. So the console put "." instead of ":" Probably this is the problem, someone knows why the console insert the wrong separators? Thanks

Hi Tiziano. Can you attach a screen shot of the page to input MAC address? Thanks.

Hi all, It's a Regional Settings problem. With Italian (Italy)format in the wizard I've got "." separators. With English (US) Format I've got ":" separators and the wizard finish without errors. Maybe a fix is required. I'm sorry but i don't know how to attach the screen shot. I want to thanks Brett and Steven that drive me to the solution. Bye

Thanks Tiziano for raising up this issue. We point out this issue and will consider a fix for it in next version.

Thanks Tiziano! i encounteed the very same problem and it takes me 5 minutes to workaround thanks to you!Bye.Diego Castelli

Thanks Tiziano for raising up this issue. We point out this issue and will consider a fix for it in next version. Hello, we had this problem too, and this workaround helps me alot! But, is there a hotfix now or must every user change this option ?