The following are some entries you may see in your log file:

• · Valid: Finished validating sAMAccountName lynckerbauth$.
• · Operation: Searching AD for account domainname\lynckerbauth.
• · Query: (&((ObjectClass Equal computer)(ObjectCategory Equal computer)(SamAccountName Equal lynckerbauth$)))
• · CompletedOperation: No account with NT name domainname\lynckerbauth was found in AD.
• · Result: Status of the account in AD is NotExist.
• · ExistingObject: Kerberos account domainname\lynckerbauth is assigned to site 1.
• · Query: (&((|((ObjectClass Equal user)(ObjectClass Equal computer)))(servicePrincipalName Equal http/servername.domainname.com)))
• · MissingObject: The service principal name http/servername.domainname.com was not found on any container in Active Directory.
• · Operation: Adding SPN http/servername.domainname.com to account domainname\lynckerbauth.
• · Operation: Adding SPN http/servername.domainname.com to account domainname\lynckerbauth.
• · ServicePrincipalNameError: A service principal name operation failed.
• · ServicePrincipalNameError: Failed to add service principal name http/servername.domainname.com to the container domainname\lynckerbauth.
• · ServicePrincipalNameErrorResolution: Ensure that the container for the service principal name exists in Active Directory and that you have the correct permissions to create, modify, delete and verify service principal names in the target organizational unit. For more information, consult your Lync Server documentation.

To solve this simply create the Kerberos account name using the following command:

New-CsKerberosAccount -UserAccount "mtn\LyncKerbAuth" -ContainerDN "OU=Service Accounts,DC=domainame,DC=com"

$ telnet mail.server.com 25 ENTER
HELO server.com ENTER
MAIL FROM:<to_username@live.com> ENTER
RCPT TO:<replyto_username@live.com> ENTER
DATA ENTER
from:to_username@live.com ENTER
to: replyto_username@live.com ENTER
Subject: Test email ENTER
This is a test email ENTER
. ENTER
QUIT ENTER

Please use the Return key for every ENTER displayed above. 

<%@ Register Tagprefix="wssuc_portal" Namespace="Microsoft.SharePoint.Portal.WebControls" Assembly="Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

This imports from the Microsoft.SharePoint.Portal.WebControls assembly and if referenced by the tag “wssuc_portal”, of course you can use any unique tag here as long as you reference the same in your code.

You  now need to simply insert the highlighted code right before the control that displays the Welcome message. If you want the picture after then place the wssuc:MUISelector control.

Running “sfc /scannow” had reported the following errors:

After several support escalations my only options was a re-install, which I obviously did not want to go through. So I decide that I would take a chance at hacking the registry in an attempt to remove any references to this update. Of course this is a very dangerous procedure not then again no more grave than having to re-image. Either way I was going to reimage so the chance of avoiding such would be a little gift to myself.

I basically search for anything related to “KB2667402” and started deleting all entries and hives. There are Windows Update specific entries that I could not delete due to permission issues. Once I deleted what I could I went back and tried to do an uninstall of the KB2667402 and this time it succeeded. I couldn’t believe my eyes.

I then went back to try the Update again and it succeeded with no issues whatsoever Never thought seeing the all green successful install message would feel so good:

To activate the shortcut press the Windows Key + the listed key...

B - Move focus to notification tray
C - Show Charms menu
D - Show Windows desktop
E - Launch Windows Explorer
F - Show Metro File Search screen
G - Cycle through desktop Gadgets
H - Show Metro Share panel
I - Show Metro Settings panel
J - Switches focus between snapped Metro applications
K - Show the Devices panel
L - Lock PC
M - Minimise all Windows on the desktop
O - Lock device orientation
P - Choose between available displays (Projector)
Q - Show Metro Search screen
R - Show Run Dialogs
T - Cycle through Taskbar icons
U - Show Ease of Access Centre
V - Cycle through toast notifications
W - Show Metro Settings Search panel
X - Show Power User Commands or Mobility Centre
Z - Show the App Bar
1 to 9 - Show/Launch Application from Taskbar
Page Up/Down - Moves tiles to the left/right
Tab - Switch between applications
, (comma) - Aero Peek (desktop)
. (full stop) - Snap Metro style app to right side of the screen
Shift . (full stop) - Snap Metro style app to the left side of the screen
Space - Switch input language and keyboard layout
Enter - Launch Narrator
Arrow keys - Aero Snap (desktop)

Simply add the present URL as an Alternate Access Mapping for the Central Admin web application and all should be good.

Whew!!!

To enable NetBIOS domain names

1. Verify that you meet the following minimum requirements:

• See Add-SPShellAdmin.
• You must read about_Execution_Policies

2. Copy the following code and paste it into a text editor, such as Notepad:

    

   $ServiceApps = Get-SPServiceApplication
   $UserProfileServiceApp = ""
   foreach ($sa in $ServiceApps)
     {if ($sa.DisplayName -eq "<UPSAName>") 
       {$UserProfileServiceApp = $sa}
     }
   $UserProfileServiceApp.NetBIOSDomainNamesEnabled = 1
   $UserProfileServiceApp.Update()
       

3. Replace <UPSAName> with the name of the User Profile service application.

4. Save the file, naming it EnableNetBIOS.ps1.

   Note:

   You can use a different file name, but you must save the file as an ANSI-encoded text file whose extension is .ps1.

5. On the Start menu, click All Programs.

6. Click Microsoft SharePoint 2010 Products.

7. Click SharePoint 2010 Management Shell.

8. Change to the directory where you saved the file.

9. At the Windows PowerShell command prompt, type the following command:

    

   .\EnableNetBIOS.ps1
       

More often than not the Time Zone issue is usually the cause, once this is corrected the services should move to Started mode.

Piggery projects can start off as small as 1 to 5 sows, but when you graduate from that into say 50 to 500 sows this becomes a commercial project that not only requires increased capital but also thorough process analysis with an eye on efficiency. For the benefit of those new to piggery, the number of sows determines the output capacity in terms of pigs available for sale (growers) from a particular farm. For instance a 50 sow piggery project might end up having average 8 to 10 litters per month. Each litter can give you around 10 piglets which means. This means after at least 6 months the same farm can have about 80 growers available for sale each month.

We are currently targeting to be a 400 sow facility over the next 18 months. Though our facility can accommodate over 800 sows, we choosing to be cautious in our approach. Once we get to 100 sows we will probably hold steady for a while until we perfect our feed systems, vaccination regimens, and distribution channels. Once all those are in place and accounted for then we will continue the march to our 400 sow target.

Of course I had no prior experience with pigs, but this recent occupation has gotten me interested in development of a piggery automation and event analysis software solution. The toughest part here is coming up with a real data models to project and forecast herd growth, food consumption, estimated number farrowing's per month etc. With this model, which I will obviously continue to perfect I would then be able to forecast various events especially with relation to a pig’s lifecycle.

General the lifecycle is as follows:

• Birth
• Weaning
• Growth
• First Heat (Gilts)
• Service
• Lactation
• Farrowing
• Sale/Disposal

Of course these events vary depending on whether the pig is a sow, grower, or boar. The biggest challenge is that different pigs hit these events at different times so if we were keeping say 50 pigs total we would definitely be able to handle the events manually. But once you have say 700 pigs or more there becomes a need to automate these event reminders to allow workers to focus on the most needy pigs.

There are various events in a pig’s life some of which are as follows:

• Litter
• Weighing
• Disease
• Vaccination
• Feeding
• Weaning
• Moving from one Location to another
• Sale
• Death

Part of increasing efficiency perfecting the reaction and response to all these events. Data collection is also a big challenge because the system would need to know whenever vaccinations are done, weigh-ins, sales, feedings, etc. Some of the events occur very rarely so manual entry is not an issue, but those that occur say twice or more a day an automated way recording these has to be devised. As a result I am currently investigating use of Symbol handhelds at our piggery especially for events such as feeding and vaccinations.

So far we are still at the beginning of our restocking exercise, but towards the end if the year we should be north of 200 sows and should reach the 400 sow milestone a few months thereafter. There are way too many aspects to consider in piggery projects especially with regards to feed. We grow our own corn so that definitely helps reduce this bill a little bit.

I will submit some random articles every now and then as the project progresses for those with a farming interest. Hhhmmm farming and SharePoint, could be an interesting intersection.

In some cases you would also see the following in your log files:

An exception occurred when trying to issue security token: The HTTP service located at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc/actas is too busy. .

The quickest solution is to grant both “Logon as Service” and “Logon as Batch” rights. In most scenarios this should take take of the problem. However where you have complex OU and GP associations you might have to exclusively exclude the service accounts for the Deny option.