Objective – Deploy Manage and Maintain Servers

Deploy and manage server images

Install the Windows Deployment Services (WDS) role; configure and manage boot, install, and discover images; update images with patches, hotfixes, and drivers; install features for offline images.

• Windows Deployment Service Overview – Technet
• What’s New in Windows Deployment Services.
• Getting Started Guide to Windows Deployment Services
• Diver Servicing Command Line Options
• DISM Technical Reference
• Service a Windows Image
• How to Add and Remove Drivers Offline
• Deployment Imaging Servicing Management (DISM) Cmdlets in Windows PowerShell

I have created a dedicated page to this as it will be a work in progress as I make my way through the objectives

If you have had hands on experience with the other Server OS’s then the knowledge you have already in DNS, AD, DHCP etc then all you really need to do is make sure you know how they are all installed and configured in Server 2012. Make sure you know Hyper-V inside out both from the GUI and by using PowerShell, I had quite a few questions on that area. The other area that my exam focused heavily on was Active Directory and Group management. Another thing make sure you know the basics of Local Storage, Raid-5, Stripped Disks, Spanned Disks and Mirrors.

Any onto the 70-411 exam, as there are no official MS Press Books available until later in the year I am going to use the 70-417 Book as apparently maps to to all the objectives, as Michael Bender suggests. In conjunction with that use the wiki resources created over at Born to Learn.

After some research this is the command that did the trick.

Netsh int ipv4 add address Interface Name ip address skipassource=true

Where Interface Name is the name of the Network Connection and IP Address is the address you wish to assign.

Remove-SPWOPIBinding –All:$true

After some research it turns out the account that the service uses needs to be in the Local Administrators group of the server that you are running it on. So after adding the account, in my case sp_farm, to that group and trying to start it again it still DID NOT WORK.

They Key and Resolution: After adding the account to the Local Admins group of the server, Restart the Sharepoint Timer Service.

Then try and start the User Profile Synchronization Service again and all should be hunky dory!.

Problem: When clicking the Follow button in the top right hand corner of the page you receive this error with an awesome description:

Pretty clear huh!…..

Well after going through the Sharepoint 2013 logs located here: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS I noticed this error in the log file : “Cannot open database “WSS_Content_576554434566776ef777ce6″ requested by login. The login failed. Log in for user ‘domain\username’.

Onto the SQL Server I go and open up Security > Logins and find the user. Right Click > Properties and select User Mapping. Find the database in the list that matches the one from the error log file, give it a tick, then in the database role membership window below put a tick next to SPDataAccess.

Close your SQL Management Studio, go back to your Sharepoint site and find a document or site to follow and click the follow link up top and bingo, you can now follow sites and documents.

Happy Sharepointing.

As always if you would like to share your tips, tutorials and tricks then shoot me and email with your stuff!

The first issue I was having was that the Generating Server was not generating the OAB correctly. Probably not a good thing if people need to the Global Address List. So I hunted through the Event Viewer and found errors pertaining to the System Attendant “Microsoft Exchange System Attendant failed to read the membership of the Universal Security Group”. Now what I did here was to RESTART the System Attendant Service and that fixed those errors. From my research I gathered that the System Attendant caches some information regarding Globsal Catalogue Server and other information. We had been moving the FSMO and GC Roles around so that would have been the issue there.

So then I opened up the Exchange Management Console and navigated to Organizational Configuration > Mailbox > Offline Address Book and removed the current OAB and created a new one, then right clicked it and selected UPDATE. I then went back into the Event Viewer and checked for errors and there were none. I wanted to double check that the OAB has been generated correctly so I ran this command from the Exchagne Management Shell.

Get-OfflineAddressBook | fl

Take a look at the output and note the GUID then navigate to C:\Program Files\Microsoft\Exchange Server. You should see a folder in there called ExchangeOAB and it should be shared. Inside that folder there should be another folder with the name of the GUID that you noted down from the above command.

What should happen now is that it should be replicated using The FDS (File Distribution Service) that is located on the CAS Server. This is resbonsible for the replication of the OAB from the Generating Server to the CAS Server, my problem is that it is NOT replicating. The generating server has the files but the CAS Server doesn’t. Therefore my clients get this error when syncronizing.

15:02:18 Microsoft Exchange offline address book
15:02:18 Not downloading Offline address book files. A server (URL) could not be located.
15:02:18 0X8004010F

Now if I check on the CAS Server I get a Successful Event like this.

Log Name: Application
Source: MSExchangeFDS
Date: 9/12/2008 8:22:34 AM
Event ID: 1008
Task Category: FileReplication
Level: Information
Keywords: Classic
User: N/A
Computer: CAS-SERVER
Description:
Process MSExchangeFDS.exe (PID=2332). Offline Address Book data synchronization task has completed successfully. OAB name: “FHS Offline Address Book”, Guid: 81319159-bded-41dc-916e-41cf99eb59b5

But when I looked on the CAS Server in this location C:\Program Files\Microsoft\Exchange Server\Client Access\OAB there is nothing there????? Anyway it was late and I thought I would wait and see if it replicated overnight. I came in the next day and checked and there we have it, the OAB replicated !!! Whoo Hoo.

But

The Clients were still receiving the error above “Not Downloading the Address Book”. I configured the OAB distribution using Web-Based Distribution. Now we are going through an ISA 2006 Proxy Server so I had a look at the Logs on the ISA Server and noticed that when the clients are downloading the address book that it is being rejected at the ISA Server. So to bypass this all you need to do is place the FQDN of the CAS Computer in the Web Proxy Tab of your Internal Network and the clients will then go directly to the CAS Server.

Now there are TON of people getting this these types of errors so I hope this will help a few of you out in troubleshooting this issue.