Creation by Ankur the ' IT Guy '

Hi Folks Below link is really helpful for dealing with 1603 error code so thought to share…. https://support.microsoft.com/en-us/kb/834484 Following also could be the possible causes 1 .        Presence of higher version of same application. 2.        Specific installation sequence is required for Application and Prerequisites. 3.        Windows installer service is corrupted. In this case unregister windows installer service and register back. 4.        Higher Windows installer version is required, at least should be 3.0 or Higher. 5.        Insufficient access permissions . Cheers.....

The SCCM clients receive their SUP/WSUS settings as a local policy on the clients, Scan gets initiated as per configured schedule and happens on base of update GUID. Location services looks for our nearest SUP. This also can be checked in windowsupdate.log When scan is completed. ScanAgent reports that the scan is complete and records the results of the scan in the updatestore. Information can be checked in updatestore.log Client sends result of scan cycle through status massages with topic ID 501 and 500 to MP and site server for each the update that are missing on machine. This can be checked in statemassage.log Once all this process completes updates evaluation gets start by receiving policy for applicable updates. Scan gets initiated for to have latest scan data update applicability and report status, This information can be checked in updatedeployment.log Client Retrieve needed update components through CIAssignment and then SDM agent checks what binaries ar...

Hi Guys... Microsoft has added support for linux and unix systems from SCCM 2012 SP1. You can easily manage supported linux & unix operating system from SCCM. You can use collections as same way you use collections to manage to other clients.Supports both direct membership and query based type. Respective Client packages are available at below link http://www.microsoft.com/en-in/download/details.aspx?id=39360 Supported UNIX/Linux Client: ·          AIX Version 7.1, 6.1, 5.3 ·          Solaris Version 11, 10, 9 ·          HP-UX Version 11iv2 , 11iv3 ·          RHEL Version 6 , 5, 4 ·          SLES Version 11, 10, 9 ·          CentOS Version 6, 5 ·          Debian Ver...

Hi Guys... This post is all about Windows Deployment service WDS and its Errors and solutions. WDS is used to deploy Operating System Images and also is SCCM OSD Component. Many times we all have faced WDS issues and errors. Following are Some of Issues and their solutions Error 10048 Description: The Windows Deployment Services Server service terminated with service-specific error 10048 This issue occurs if the following conditions are true: ·          The DHCP server and the WDS server are installed on the same computer. ·          The  Do not listen on port 67  option is  NOT  enabled in the DHCP tab. Cause When the DHCP server and the WDS server are installed on the same computer, the WDS Service tries to use the port 67. However, the DHCP server already uses this port. Solution: Method 1 At the command prompt, type the following command, and th...

Hi guys, This time we will look on SCCM 2007 to SCCM 2012 Migration. SCCM 2012 is out there in market and it provides lots of cool new features  for it infrastructure management like New CAS site, HTTP & HTTPs communications, Application catalog , enhanced mobile devices support, support for Linux & Mac Clients, Enhanced reporting, Monitoring, ADR-Automatic deployments rules…..So list is really quite large . So these are some differences which make you to think about SCCM 2012. If still you are running SCCM 2007 in your environment, you should think about SCCM 2012. How you can upgrade to SCCM 2012? There is no In-Place Upgrade option to upgrade from SCCM 2007 to SCCM 2012. You need to perform a Side-by-Side Migration for SCCM 2012. What Migration exactly does? When you migrate data from a source hierarchy, you access data from the site databases that you identify in the source infrastructure and then transfer that data to your current...

Hi Guys, Again i am back with very common information about DHCP,WDS & PXE and issues troubleshooting and their solutions. DHCP, WDS, and PXE are the main and needed components which plays very important role in SCCM OSD. They function and provide a very cool and automatize the OS installations (Network based). So why is the Need? DHCP : DHCP offers automatic ip address assigning functionality to machines at both booting state and online state. DHCP Scope options are one main key component. WDS : WDS offers the PXE functionality (Not SCCM) for network based OS installation (boots machine in to windows installation mode from network) So when we install the SCCM PXE service Point on WDS Server, It just overrides the settings of WDS PXE. Now Common PXE Boot Issues: ·         PXE-E53: No boot filename received   ·         PXE-T01: File not found ·    ...