The first thing you will need to do is create a separate certificate template to create the SCCM client certificate to be used for your workgroup computers. Create the certificate template Open the Certification Authority console, right-click Certificate Templates, and then click Manage to load the Certificate Templates management console. In the results pane, right-click the entry that displays Workstation Authentication in the column Template Display Name, and then click Duplicate Template. In the Duplicate Template dialog box, ensure that Windows 2003 Server, Enterprise Edition is selected, and then click OK. In the Properties of New Template dialog box, on…

If you want to run a report of mobile devices connected to Exchange 2007 or Exchange 2010, the two PowerShell commands will export the results to CSV format. Just copy and paste into notepad and save as a script.PS1, then run (./script.ps1) from the Exchange Management Shell. Exchange 2007 $devices = @() $mailboxes = Get-CASMailbox -ResultSize:Unlimited | Where-Object {$_.HasActiveSyncDevicePartnership -eq $true -and $_.ExchangeVersion.ExchangeBuild -ilike "8*"} foreach ($m in $mailboxes) {     $devices += Get-ActiveSyncDeviceStatistics -Mailbox $m.Identity } $devices | Export-Csv DeviceStats.csv Exchange 2010 $devices = @() $mailboxes = Get-CASMailbox -ResultSize:Unlimited | Where-Object {$_.HasActiveSyncDevicePartnership -eq $true -and $_.ExchangeVersion.ExchangeBuild -ilike "14*"} foreach…

You can move Hyper-V virtual machines in a Windows failover cluster or on a stand-alone Hyper-V host. Moving virtual machines is a fairly easy process, without having to do too much work at the file level, it’s mostly an export and import process. In this example, I will cover how to move virtual machines in a Hyper-V failover cluster environment, which is very similar to a stand-alone Hyper-V host. This will cover off moving the .VHD and .XML configuration files together. Export process Power down the Virtual Machine you plan on moving Export the Virtual Machine to the top level…

  For your Exchange 2010 DAG POC, you will need 4 virtual Windows Server 2008 R2 servers. Domain controller & DNS Exchange Hub Transport server (Witness server and witness directory) Exchange Mailbox & Client Access Exchange Mailbox Not only will you need 4 Windows Server 2008 R2 servers (3 Exchange servers & 1 Domain Controller (DNS)), you will also need 3 Windows 7 Enterprise client machines. All software is available Microsoft: Exchange 2010 with SP1 (180 day evaluation) http://technet.microsoft.com/en-us/evalcenter/default Windows Server 2008 R2 (180 day evaluation) http://technet.microsoft.com/en-us/evalcenter/default Windows 7 Enterprise (90 day evaluation) http://technet.microsoft.com/en-us/evalcenter/default Office 2010 Professional Plus (60 day…

You may be having trouble deploying an operating system to a brand new machine even after you have advertised an OS deployment task sequence to it’s correct MAC address. You might be receiving any one of the following errors: PXE Boot aborted. Booting to next device MAC=70:71:BC:88:C3:BC SMBIOS GUID=00000011-4918-8015-BF5A-888888888788 > Device found in the database. MacCount=1 GuidCount=1 The SMS PXE Service Point intructed device to boot normally since it has no PXE advertisement assigned The SMS PXE Service Point instructed device to boot normally since it has no PXE advertisement assigned Generally on any machine the MAC address and the…

To grant access to remotely open the Configuration Manager 2007 R3 console requires the following steps: Ensure the user is a member of the SMS admins group on the SCCM server Use the DCOM tool to add remote launch permissions to that group – straight out of the help file: To grant Remote Activation permissions to the SMS Admins group From the Start menu, click Run and type Dcomcnfg.exe. In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer. On the Action menu, click Properties. In the My Computer Properties dialog box, on the…

Client installation log file located on the client: %windir%\system32\ccmsetup\ccmsetup.log …or %windir%\ccmsetup\ccmsetup.log Installing the SCCM client manually is a simple case of running a command directly from the SCCM site share. \\servername\SMS_<sitecode>\Client\ccmsetup.exe A number of command line options are available if the Active Directory Schema hasn’t been extended for Configuration Manager 2007, these options are not needed if AD has been extended and Publish this site in Active Directory Domain Services is selected in the Advanced tab of the Site Properties dialog box, then client computers will automatically search Active Directory for installation properties. /mp:SMSMP01 – Specifies the management point SMSMP01…

One of the fundamental things you need to do with any SCCM installation and deployment, you need to get the basics right. Queries are those basic building blocks which everything else in SCCM is based on. Once you have all your custom queries setup, then you can setup collections based on the queries, once this is done, all other SCCM components is relatively strait forward. A good way to target separate machines in queries and collections is by their Chassis Type. Chassis Types 1 Other 2 Unknown 3 Desktop (Virtual machines as well) 4 Low Profile Desktop 5 Pizza Box…

msiexec /Option <Required Parameter> [Optional Parameter] Install Options </package | /i> <Product.msi> – Installs or configures a product /a <Product.msi> – Administrative install – Installs a product on the network /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>] – Advertises a product – m to all users, u to current user </uninstall | /x> <Product.msi | ProductCode> – Uninstalls the product Display Options /quiet – Quiet mode, no user interaction /passive – Unattended mode – progress bar only /q[n|b|r|f] – Sets user interface level         n – No UI         b – Basic UI         r – Reduced UI        …