Posts

Showing posts from June, 2015

Just in Kace

We have a Kace appliance. A Kace 1000. We "found" this a couple of weeks back and I was duly dispatched to set about configuring and understanding it. After some help from Dell we obtained a DVD to re-image the appliance to v6.3 I am now in the process of sorting out the LDAP integration (done) Patching Windows (done) Dell (done) 3rd Party (done) software installation (done) agent provisioning (almost there!) More news when I have finished things. Oh and thanks to those @ ITNinja! http://www.itninja.com/

Office 2013 KMS....Did you click No?

Image
Annoying there is lots of information on activating Office 2013 client side but nothing on activating the KMS host - over the internet... It looks like someone panicked at this question and choose No.... This meant that our Office was not activating as expected. Nothing on the interent showed me how to fix this as no-one it seems chooses No. Well no one who wants to use the internet to activate Office KMS that is. Simply bumbling through led me to try C:\>cscript slmgr.vbs /ato 2E28138A-847F-42BC-9752-61B03FFF33CD And Bingo! After 5 attempts were made to the KMS host all was active!

SCCM Server build not building onto C drive?

I've recently come into contact with SCCM. I love it. I also love MDT.  So I was pleased to see that they are tightly integrated!  Hoorah! I set about creating an MDT build task within SCCM, easy right? Well...yes. Initially. Err you can't PXE boot to MDT and SCCM.  Unless you follow this website.  Awesome! http://blogs.technet.com/b/deploymentguys/archive/2011/09/07/co-existing-pxe-boot-for-mdt-standalone-image-capture-amp-configmgr-image-deployment-environments.aspx Once I'd got MDT responding to MDT known computers I got the MDT server 2012 build working and was able to get a captured image.  Straight forward an no different to the hundreds of MDT tasks I've set up before. I then had some learning to get this MDT capture into SCCM.  First there was the requirement for an MDT package...This turns out to be the entire MDT deployment point folder structure - including all the scripts.  Far enough.  Then I needed an MDT configuration, this turns out to b