SCCM 2012 SP1 Client Push Error for x64 bit client

      

        Error : Failed to get client version for sending messages to fsp

I have a lab set up for System Center Configuration Manager 2012 server with SP1 upgraded, set up installation was successful with all the site system roles updated and configured.

When I try to push ccm client on Windows 7 machine(x64 bit) through client push installation method it gave error as “failed to get client version for sending messages to fsp” along with “Failed to get DP locations as the expected version Error 0x87d00215” these errors were found on ccm.log file on client machine and on site server ccm.log gave only error as “enable to connect to WMI root’ which rectified after adding site server machine name on administrators group on client machine and after editing system account settings on distribution point.

After doing some search on Google about this particular error I thought it could be because of the known issue stated on internet which said “This is a known issue in SP1 when installing the 64bit client. You will need to apply this hotfix to your site server and update the ConfigMgr installation package on your DP's” hence I have downloaded the hotfix available for the same from Microsoft website: http://support.microsoft.com/kb/2801987 applied the hotfix on site server machine which updated the client packages then tried to re-push the client package but it gave the similar errors on ccm log files. I checked distmgr.log file for to check for any traces there which said “failed to process package CA00000#”

Therefore I had decided to test this by removing the DP for package assignment hence

1.       Removed the DP role from the Primary Site server – checked the DistMgr.log for the removal.

2. Re-deployed the DP role to the Primary Site server – checked  the DistMgr.Log/ Distribution Point Configuration State for the installation

       Somehow this fixed the issue, It installed the cm client on windows machine successfully.

There are currently no logon servers available to service the logon request

 

 

Error : "There are currently no logon servers available to service the logon request" 

After joining the machine to the domain when I tried to login for the first time with domain administrator credentials it said "There are currently no logon servers available to service the logon request" and yes again I had to Google about the error and try resolving the error most of the solutions available online spoke about WINS database entries for authentication and domain controllers entries with NetBIOS names along with WINS server. I tried the following things to get the issue fixed.

1.        Rebooted machine

2.       Logged in with local administrator account

3.       Disabled firewall for testing

4.      Tried to ping the Domain controller it pined and was able to resolve domain name

5.       Disconnected the machine from domain and reconnected again

6.      Rebooted machine again and tried to login with domain user as earlier.

This fixed the issue though but I am not sure if this has anything to do with firewall settings or may be it takes some time to update entries on DC or DNS server after adding the machine to domain and trying to login with domain credentials for the first time.

 

Differencing Disks in Hyper-V

A differencing disk is type of virtual disk which is used in cases where one wants to isolate the changes made to guest OS or the virtual hard disk attached to that particular virtual machine. The main thing which required for this differencing disk is to have the disk to be associated to exist before creating one. Where one can you inspect disk option to check the associativity of the disk to its parent disk or you can use reconnect option (all these in Hyper-V environment) hence making differencing disk ready to store all changes which would have been stored in parent disk which makes sure of no alterations to parent disk. It stores data dynamically as data is written to it and can grow as large as the maximum size allocated space for parent disk while creating it.

Content stored in these disks can be merged with parent disks if required but this alters parent disk and merging it to new virtual disk helps retain both of them with contents of both the disks. Which means many differencing disks can share one parent disk and have their own differencing disk.

This feature is particularly useful where you have many virtual machines which can share same parent disk which can store operating system and differencing disk storing the configuration that is different from parent. We have to be careful in locking the disks other than most recent child disk making child disk writable which helps in validating the chain of differencing disks in those consecutive versions.