15:52:29,085 INFO HP. (:0) - (MIKSCCM.cs:67) - Site Server Name = **OUR SERVER**, Site Server Code = CVG 15:52:29,085 INFO HP. (:0) - (MIKSCCM.cs:59) - Retrieving SCCM Connection Object from SmsCustomDialog ConnectionManager property 15:52:29,048 INFO HP.Templates.WizardTemplate (:0) - (WizardTemplate2.cs:123) - Server Name = **OUR SERVER**, Site Code = CVG 15:52:28,905 INFO HP. (:0) - (MIKSCCM.cs:67) - Site Server Name = **OUR SERVER**, Site Server Code = CVG 15:52:28,905 INFO HP. (:0) - (MIKSCCM.cs:59) - Retrieving SCCM Connection Object from SmsCustomDialog ConnectionManager property 15:52:28,904 INFO HP.Templates.WizardTemplate (:0) - (WizardTemplate2.cs:110) - MIKCore get Instance called. 15:52:28,904 INFO HP.Templates.WizardTemplate (:0) - (SCCMContextMenuHelper.cs:26) - Feature string = BIOS Configuration, feature type = BCU_POLICY 15:52:28,903 INFO HP.Templates.WizardTemplate (:0) - (WizardTemplate2.cs:82) - InitialiseCMConnection 15:52:28,902 INFO HP.Templates.WizardTemplate (:0) - (WizardTemplate2.cs:323) - WizardTemplate2_Load 15:52:28,882 INFO HP.Templates.WizardTemplate (:0) - (:760) - Window width = NaN, Height = NaN Have been able to use MIK to download a driver pack and deploy BIOS update, MIK client and BCU to a test machine, so the main functions of MIK appear to be working alright in ConfigMgr, but need to be able to bulk update BIOS settings for our fleet. This is my first try to make a BIOS Config policy so unable to try editing an existing one. Below is the log output from the time i selected to creat a new BIOS Config Policy. I too am experiencing that same error in the MIK.log on a new MIK installation.ĬonfigMgr ver 2006.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |