Configure and Manage Distributed File System (DFS)

Comments

Post a Comment

Popular posts from this blog

SCCM PXE Error after booting – The certificate associated with this media has expired

Image
Issue: OSD Stops working as "Client Distribution point certificate" has expired Error: PXE-053 No boot file name received. Description:   Today when i tried to boot a computer we started witnessing above error message. Immediately i opened "SMSPXE.log" file and found following string Certificate [Thumbprint A0CADB6E2DA5CBAFB8860F5054A50FC011F80D53] issued to 'PRI' Server has expired. SMSPXE 9/29/2014 4:05:02 PM 2472 (0x09A8).  Also you'll start receiving this error message on TS before certificate gets expired. Solution: Renew the Distribution Client Certificate using below steps: 1. Log in to Primary site server, open mmc and Add "Certificates Snap-in"  2. Under Personal Ceretificate store, you will find distribution point certificate 3. Right click on it " Request Certificate with New key and Click enroll". 4. Export this certificate with private key and import in distribution point setting...
Read more

Rearm the Office 2013 installation

Image
There is a 25-day grace period from the time of installation of Key Management Service (KMS) clients before notifications to activate are displayed to the user. If you want to deploy an image, you must rearm your Office 2013 installation before you capture the image. If you do not rearm, users see notification dialog boxes at the time that the image is deployed, instead of 25 days after deployment. The 25-day grace period gives ample time for a KMS host to be found and activation to succeed. If activation is successful, users do not see notifications to activate. Rearm the Office installation Rearming does the following important tasks: Resets the grace timer to 30 days. Freezes the grace timer until either an Office application is run, or the ospp.vbs script is run. Resets the client computer ID (CMID). This is important because the KMS host uses the CMID to determine the num...
Read more

Computers not joining domain in SCCM task sequence

Image
Issue:   I recently created a new TS and edited the LDAP path to change the OU where the computers get added. However, the machine fails to join the domain. Resolution:   Check the logs c:\windows\debug\NetSetup.log. and if you find the error shown in red, might be the service account which is  been configured to join in domain may not have the permissions to put objects in that OU. Get those permission from AD administrator, it should work then hopefully. Additionally you can check the smsts.log  Reference: http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/40c208fb-51cc-4bb8-ad88-7a46e10399f0/
Read more