![]() ![]() $inParamsAddEntry.MACAddress =$mACAddress.Text $siteClassString=”\\$siteProviderName\root\sms\site_$siteCode” ”:SMS_Site” The basic powershell to add a computer account to SCCM: In normal circumstances, the technician would open the SCCM console, find the collection with the TS advert and drill-down through the OSD Node, to import the computer using the wizard. I created a simple tool in Powershell which they could run from their desktop and easily add a new laptop or computer for OS deployment.įirst of all, and i won’t go into too much detail here, i set up an OSD Task Sequence, a Collection and advertised the TS. ![]() ![]() They wanted to quickly add in new hardware to receive OSD Task Sequence Advertisements via PXE. I identified a need for a customer to carry out basic tasks, such as Import Computer Information. Knows the applications, the estate, the environment.įor FDs and IT Management, the built-in Reports may well be enough to get information on the estate and inventory, with R2’s Reporting Services Point enhancing this functionality.įor Technicians, those who will be running and maintaining the SCCM environment and carrying out the deployment and administrative tasks with SCCM the MMC console can be a maze of nodes and components. Has (hopefully) documented the deployment and operational processes they want to streamline. ![]() IT Technician: More interested in the technical aspects. May want to get under the hood, but without training not advisable. IT Manager or similar: Probably wants deployment processes streamlined for their staff, to enable them to work more efficiently. Wants to know what IT equipment and licensing they have. So until the launch of 2012 with it’s lovely interfaces and user-friendly-centric operations how can i enable my customers to carry out day-to-day tasks in SCCM?įirst of all identify the key stakeholders: Who wants SCCM? Who needs SCCM? Why do they want it? What role in the business do they expect it perform?įD: Paying for this new technology, wants return on investment. With 2007’s MMC Console it can be a bit daunting for them, so much information, and the access security is not what it should be. But i deploy it at customer sites and as a rule the technicals who are to run and operate it once i have gone have not taken any form of SCCM training. Yes, ConfigMgr 2007 is fantastic, i love it. I can’t wait to get ConfigMgr 2012 up and running. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |