Been a While…

Just thought I would update the Blog with “Windows Live Writer”, but that turned into a 2 day ordeal. As you can see it is now working and here is what I found:

From Microsoft Answer

Question

CB Blogger asked on March 5, 2012

Cannot connect Blogger account to Windows Live Writer

Question Summary
Other Windows Live Writer issues

What blogging service are you using ?

Blogger

Is your computer behind a corporate firewall ?

No

Enter the exact error that you are experiencing :

Can't connect to your blog service: unable to connect to the remote server.

Additional Details

When I try to link my Blogger account to Live Writer, I first get the message "Windows Live Writer was not able to automatically detect your blog settings. Please select the type of blog you are using and continue".
I select Blogger and hit next and then get the message "Can't connect to your blog server. Unable to connect to remote server. Please try fixing the problem and try again".
I went into the control panel and updated Live Writer.
This is my home computer with Windows Essentials for security...not sure about firewall or something that needs to be set in Blogger first? Any help would be greatly appreciated...I have already spent hours on this.

Answer

Asheej T K replied on October 23, 2014

MVP

I am answering to this question after few years because it may help someone.

Recently google changed thier security policy and it blocks access to the blogger from all external tool like live writer or any other tool which can be used to write blog posts.

What you can do to over come from this issues is,

go to https://www.google.com/settings/security

and then go to the section Account permissions and click on Settings against "Access for less secure apps"

Here you have to enable the "Access for less secure apps" and click on Done.

Now you try to access the same.

Let me know if anybody is still facing this issue.

*********************************************************************************

Worked for me!

Reduce Windows 7 WinSxS Folder Size by Chris Stinson

Reduce Windows 7 WinSxS Folder Size

Posted By Chris Stinson in Windows on June 23, 2011

With Windows Vista, the WinSxS folder was able to be cleaned up via a third party tool (WinSxS Lite here – Vista only!). With the initial release of Windows 7, we lost that capability – but it has since returned with Service Pack 1.

The WinSxS folder is used to store install and uninstall files, windows packages (current and previous versions of a component) and out-of-band releases. You should not completely delete this folder. Post Windows 7 SP1, there is now a way to remove the unnecessary files from this folder using the command line (elevated/admin mode -> Click Start -> Type “cmd” in Search. Right click on “cmd” and choose “Run as Administrator”). This is great for reducing the Windows folder size for SSDs and netbooks. In my case it saved 3.5GB of space.

dism /online /cleanup-image /spsuperseded



Before:



After:

Relative URL's don't work in SharePoint 2010 when using a custom sitemap

Relative URL's dont work in SharePoint 2010 when using a custom sitemap

thanks to by StephanieDonahue.

SharePoint “Read-Only” it’s a feature…

Recently we put a site into read only and we got locked out of the site after a possible timer had ran. The issue was a page that was still in “draft” mode, once it was published all was well. Here a query to run against the database to check for those files.

 

SELECT

NN.Url AS URL,
UIVersionString,NN.ElementType,[Level]

FROM AllDocs (NOLOCK) AD
JOIN NavNodes (NOLOCK) NN ON
AD.WebID = NN.WebID
AND NN.Url LIKE '%' + AD.LeafName + '%'
WHERE
[Level] = 2 /* Draft Version */
AND UIVersionString LIKE '0.%' /* Never Published */
AND NN.ElementType = 1 /* 0 = Page, 1 = Link, 2 = Dynamic Page */

Isolated Environment Issue

Original Article

Thanks ColorNila

When you try to configure SSO in MOSS, it may fail with an error like this one:

User CONTOSO\SSO failed to configure the single sign-on server. The error returned was 0x80070995. Verify this account has sufficient permissions and try again.

It sounds like the SSO service account contoso\SSO seems to have permissions, huh? Here are the troubleshooting tips for the issue:

Variables:

Let us consider the following details (variables :) ) for this issue scenario:

Farm service account: contoso\SPSVC

SSO administrator account: contoso\SSO

FQDN name of the SharePoint server: MOSSBOX.contoso.com

Step 1: Confirm SSO accounts are set with correct permissions

As mentioned in Plan for single sign-on (http://technet.microsoft.com/en-us/library/cc262305(office.12).aspx#section4) , make sure the SSO accounts are set with correct permissions / privileges. It is one of the important steps for the troubleshooting of the issue.

Step 2: Confirm whether the name resolution works correctly

Let us find out the current logged on Domain information using the command: Set U

From command line, type: set u

The result may be something like this:

USERDNSDOMAIN=CONTOSO.COM
USERDOMAIN=CONTOSO
USERNAME=SPSVC
USERPROFILE=C:\Documents and Settings\SPSVC

Now let us find the logged on domain controller information using the command: Set L

From command line, type: set l

The result may be something like this:

LOGONSERVER=\\DC1

At this stage, let us find out the PDC emulator role holder in the domain using the command: netdom

From command line, type: netdom query fsmo

The result may be something like this:

Schema owner                Box1.CONTOSO.com
Domain role owner           Box1.CONTOSO.com
PDC role                    DC1.CONTOSO.com
RID pool manager            Box3.CONTOSO.com
Infrastructure owner        Box3.CONTOSO.com
The command completed successfully.

According to the above command line, the PDC emulator role is set with DC1.CONTOSO.com

That said, let us use the command nltest which uses DNS queries to resolve the PDC emulator in the same way that  any application would resolve.

From command line, type: nltest /dcname:contoso

You may get a result something like this:

NetGetDCName failed: Status = 2453 0x995 NERR_DCNotFound

**************************************************************

Original Article

Thanks Daniel Petri

1. On any domain controller, click Start, click Run, type Ntdsutil in the Open box, and then click OK.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\WINDOWS>ntdsutil
ntdsutil:

1. Type roles, and then press ENTER.

ntdsutil: roles
fsmo maintenance:

Note: To see a list of available commands at any of the prompts in the Ntdsutil tool, type ?, and then press ENTER.

1. Type connections, and then press ENTER.

fsmo maintenance: connections
server connections:

1. Type connect to server <servername>, where <servername> is the name of the server you want to use, and then press ENTER.

server connections: connect to server server100
Binding to server100 ...
Connected to server100 using credentials of locally logged on user.
server connections:

1. At the server connections: prompt, type q, and then press ENTER again.

server connections: q
fsmo maintenance:

1. Type seize <role>, where <role> is the role you want to seize. For example, to seize the RID Master role, you would type seize rid master:

Options are:

Seize domain naming master
Seize infrastructure master
Seize PDC
Seize RID master
Seize schema master

1. You will receive a warning window asking if you want to perform the seize. Click on Yes.

A Guide to Claims–based Identity and Access Control

or download from here.

No crawls since password change, Events 6398, 7076, 6482, 7021

Clicky

The undocumented “deleteconfigurationobject” parameter