I know it is possible to set the computer name before you start the task sequence by adding the OSDComputerName variable to a collection – usually used in the Unknown Computers collection. I know as well how to generate it based on the serial number of the workstation or laptop. Well, this was not enough for me and I decided that it should be possible to auto-assign computer names during Task Sequence based on the current active directory names. To make it even more fun I was determined to get the next available computer name based on domain naming convention (will shorten this to DNC), but only for computers above 1000. Please, do not ask… Read More »SCCM/MECM How to set computer name automatically during Task Sequence
If you have to change the Report Server service account password (never happens, right?!?) do yourself a favor and before rebuilding the entire report service go to Administration –> Security –> Accounts, double click on the account in question, click SET and enter the new password. Symptoms are: 1. Cannot impersonate user for data source2. Cannot change data source user – you change it and it’s reverting back3. Other logon errors after reporting works for few seconds
Recently I had to install windows through SCCM and Remote Distribution point with enabled PXE support in remote site which doesn’t have an IT technician available and this turned to a challenge for a regular user. I’m using MDT Task sequence and we support secure boot. In order to make it work few settings in the BIOS needs to changed, the factory default setup wouldn’t work. Under System Configuration Integrated NIC – Enabled w/PXE, make sure that Enable UEFI network stack is checked as well SATA Operation – AHCI Secure Boot – Enabled, Legacy Support Disabled – If your environment doesn’t support secure boot disable it, however, it’s not that hard to support it in… Read More »Dell Workstations (3630) UEFI Bios settings – no bootable device found
If you had to change the sccm client site code on multiple computers (after sccm migration or new/upgraded server installation) nowadays you might have discovered that it’s not as easy as it should be. You could push the new site client to all computers generating a lot of heat to the network or try deprecated wmic (miserably fails). I wanted to avoid mass client push and found that the following quick and dirty script works well: First create a list of all computers using your favorite method, I already have a text file with them so I’ll just use it, it’s named mycomps.txt and it is in my current folder.
WSUS on Secondary Site Generally speaking if everything is OK you install WSUS role with the same setup as your primary site, launch the console once, close it, install SUP from the SCCM and configure it and that’s it. However, sometimes the WSUS breaks and when that happens it is usually a pain to get it back. These are just my two cents. Good post on SUP installation could be read here. Setting up WSUS + SUP on a Secondary Site (SCCM2012) Uninstallation TIPS: I would uninstall the WSUS and WID roles, and DELETE any resource used by WSUS. This includes: The %ProgramFiles%\Update Services folder The ~\WSUS folder tree The HKLM\Software\Microsoft\Update Services registry key. –… Read More »WSUS on secondary SCCM site
Fox x64 bit workstations: Or use the one from this Technet post select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.Caption like “%7%” and SMS_R_System.Client = 1 and SMS_R_System.Obsolete = 0 and SMS_G_System_COMPUTER_SYSTEM.SystemType = “x64-based PC” If you dont want to filter obsolete and client installed machines remove ” SMS_R_System.Client = 1 and SMS_R_System.Obsolete = 0 and” For x86 workstations: select * from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = “X86-based PC”
Create a new collection and use the following query to select inactive agents, the part in bold is to exclude all computers with name stating with PCNAME% from it if needed, % is equal to * in sql so if your naming convention is pcname01, pcname02 and so on pcname06% will exclude pcname060, pcname061, pcname0600 and so on. If you want to remove one or two names only you can use (“pcname01″,”pcname02”) instead of pcname% select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_CH_ClientSummary on SMS_G_System_CH_ClientSummary.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_CH_ClientSummary.ClientActiveStatus = 0 and SMS_G_System_SYSTEM.Name not like “PCNAME%” One of the fixes for inactive clients could be found here First part… Read More »Create an SCCM collection containing inactive clients excluding certain computers