Monday, December 30, 2019
I have migrated my blog to a WordPress site, please check the new site at https://paddymaddy.com
Wednesday, July 27, 2011
Deploy Windows 7 in Your own Way
If your last desktop OS deployment was circa Windows XP, we have some good news. Gone are the days of manual building, configuration and migration processes. New sets of tools are available to facilitate a deployment tailored specifically for your environment.
look at here for more …….
Tuesday, July 26, 2011
Good Website for MDT
Monday, June 20, 2011
SYSPREP 2003
sysprep a windows 2003 R2 image, follow the below:
- Insert CD1
- go to Support\Tools\Deploy.cab
- select everything and extract them to c:\sysprep ( a folder that you have created it)
- Double click sysprep.exe.
- Keep the default settings (Options un-selected, shutdown mode: shutdown)
- click on Reseal
- And press Ok
Hyper – V --- SysPrep Windows 2008 R2
1) Install WINDOWS 2008 R2 on the host machine
2) Add Hyper V role
3) Create a new VM to act as the base IMAGE
4) Mount an ISO version of windows 2008 or R2
5) Install the OS
6) Run Sysprep (/generalize switch enabled), Shutdown
7) Inside Hyper V manager, Export to a alternate location
8) After Export is done, copy the entire folder to your permanent location
9) Inside Hyper V manager, import the VM you copied.
10) Rename to a friendly name.
11) Fire the new VM up, run through the sysprep process and poof!
12) Make sure you chose "Copy the virtual machine (create a new unique ID)' option, this is not the default.
Tuesday, June 14, 2011
Wednesday, June 8, 2011
Tool for SAM – from xAssets for SCCM
SAM Features with xAssets -
- Configurable, Robust and Complete Reporting of all SCCM Assets
- Software Asset Management
- Options to discover Linux, Unix, Mac, IP Phone, Network Equipment into the SCCM inventory
- Integrate to Active Directory and other IT systems
- Contract Management
- Spare Parts Inventory
- Scalable to Large Enterprises
- Hosted SAAS or Locally Installed
Some good MS Blogs
The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv
Monday, June 6, 2011
Software Inventory less than 21 Days - Collection
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 where ResourceId in (select ResourceID from SMS_R_System inner join SMS_G_System_LastSoftwareScan on SMS_G_System_LastSoftwareScan.ResourceID = SMS_R_System.ResourceId where DATEDIFF(dd,SMS_G_System_LastSoftwareScan.LastScanDate,GetDate()) > 21 )
SCCM/ SMS Console Installed Systems Collection
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_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Microsoft Systems Management Server 2003 Administrator Console"
Patch Supersedence Report from SQL Query
select cir.FromCIID [New CI],
info.BulletinID [New BulletinID],
info.ArticleID [New ArticleID],
info.Title [New Title],
info.InfoURL [New InfoURL],
info.DatePosted [New DatePosted],
cir.ToCIID [SUPERSEDED CI],
info2.BulletinID [Superseded BulletinID],
info2.ArticleID [Superseded ArticleID],
info2.Title [Superseded Title],
info2.InfoURL [Superseded InfoURL],
info2.DatePosted [Superseded DatePosted]
from v_CIRelation cir
left join v_UpdateInfo info on cir.FromCIID = info.CI_ID
left join v_UpdateInfo info2 on cir.ToCIID = info2.CI_ID
where RelationType = 6
((info.ArticleID = @KBNumber) OR (info2.ArticleID = @KBNumber))
order by info.BulletinID, info.ArticleID
Microsoft Virtual Academy
Now you can learn from Microsoft Virtual Academy
Improve your IT skill set and help advance your career with a free, easy to access training portal. Learn at your own pace, focusing on Microsoft technologies, gain points and get recognition.
Tuesday, May 31, 2011
Monday, May 30, 2011
One other Great tool to fix client actions without Console (Right click tools)
I Just checked the tool and found it would useful for one works on SCCM Client health
It has key features as below
- Initiate most common SCCM client schedule actions.
- Initiate SCCM client health checks and fixes. Allows running checks with and without fixes as well as full health check.
- Initiate basic administrative actions on workstations.
- Switch between integrated authentication and alternate credentials. When logged on username has not enough rights it’s possible to specify alternate credentials by clicking on a link in top-right corner. Windows XP requires that cmdkey.exe is available in HTA folder.
- Use TXT, CSV, XLS or XLSX files as the data source. Files with TXT extension must have computer names on each line. Excel worksheets are read from column A starting from second row. Using exported CSV from SCCM console is also supported – script knows that computer names are in first column.
- Populate computer list from SCCM collection. Allows loading all collection members into a list.
- Manually enter computer names into a textbox. Allows manually entering one or more computers in a text box for quick actions.
- Supports both 32-bit and 64-bit OS on clients.
- Supports Windows XP SP2 and newer operating systems on clients.
- Displays real-time progress. Works when running HTA on Windows 7 or Windows Server 2008. Useful when there are thousands of computers and it would be nice to know how much is done. HTA window may not update as smoothly in Windows XP and Windows Server 2003, but it works.
- Log is created in a text area and in a file. Lastlog.log is written to HTA folder. By default the log is using Trace32 log formatting.
- Uses configuration file to store default settings.
Client Tasks that can be performed are classified in to 5 categories:
- 1. Client schedule actions
- Hardware Inventory Cycle
- Software Inventory Cycle
- Discovery Data Collection Cycle (Send DDR)
- Machine Policy Retrieval & Evaluation Cycle
- Software Updates Deployment Evaluation Cycle
- Software Updates Scan Cycle
- File Collection Cycle
- Windows Installer Source List Update Cycle
- Software Metering Usage Report Cycle
- Branch Distribution Point Maintenance Task
- Certificate Maintenance Task
- 2. Client agent actions
- Restart SMS Agent Host service
- Repair SCCM client
- Reset SCCM client policies
- Reassign site code
- Generate new SMS GUID
- Delete trusted root key
- Delete certificates (re-register client)
- Change client cache size
- Uninstall SCCM client
- Install SCCM client
- 3. Client health actions
- Check WMI; Fix WMI
- Check services; Check & Fix services
- Check admin$ share; Check & Fix admin$ share
- Check assigned site; Check & Fix assigned site
- Check registry; Check & Fix registry
- Check inventory; Check & Fix inventory
- Check client version
- Full health check
- Full health check with fixes
- 4. Advertisement actions
- Query advertisement status
- Rerun advertisement
- Rerun user based advertisement
- 5. Other actions
- Refresh group policies
- Ping workstations
- Execute remotely (as SYSTEM)
- Get logged-on user
- Log off current user
- Reboot workstations
- Shut down workstations
- Power off workstations
Download it from here :-- http://sccmcat.codeplex.com/
Thursday, May 26, 2011
Systems are in “A” collection But not in “B” Collection & Vice versa
ignore other collection
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 where Client = 1 and ClientType = 1 and
ResourceId not in (select ResourceID from SMS_CM_RES_COLL_XXXxxxxx)
Friday, May 20, 2011
On Windows 2008 R2 with SP1 you may face MP Fatal error 1603 Problem
This could happened because of not supported versions to fix this you need to apply a patch KB2489044. (I ran into this problem today at a customer place and fix is below)
Asset Intelligence Sync Public Certificate Expired
You may see in AIUpdateSvc.log has entries of “WebException trying to enroll: Status = ProtocolError” and “Exception attempting sync - The request failed with HTTP status 403: Forbidden.”
this could because of your SCCM Public certificate expired. yes by default Microsoft will install a public certificate that will expires on 3 years i.e., 4/25/2011.
To resolve this you need to Update the Certificates for Asset Intelligence
- Configuration Manager 2007 Service Pack 2: Install hotfix KB2483225. This hotfix installs the updated public certificate for System Center online authentication and no further action is required. As part of the hotfix installation, the updated certificate is configured for the Asset Intelligence synchronization point and your specific certificate will be automatically renewed. For more information about this hotfix, see http://support.microsoft.com/kb/2483225/en-us.
- Configuration Manager Service Pack 1: Obtain a certificate file and manually configure the Asset Intelligence synchronization point to use the updated public certificate for System Center online authentication. Use the following steps:
- Email ai-cert@microsoft.com to request a certificate file that contains the updated public certificate for System Center online authentication. Please note that this alias is for certificate distribution only and not for support questions.
- Store the certificate file in a location that is accessible to the site server.
- In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database (<site code> - <site name>) / Site Settings / Site Systems.
- Click the Asset Intelligence Synchronization point site system computer name.
- Select the Asset Intelligence synchronization point, and click Properties.
- On the General tab of the Asset Intelligence Synchronization Point Properties, specify the path to the new System Center Online authentication certificate (.pfx) file, and click OK.