-
-
English
Today, I almost missed an update of very nice tool – Microsoft SharePoint Administration Toolkit. I browse to Microsoft SharePoint Team Blog, – found out that they already announce the 4th release last week.
But before you can play around with the tools, you will need to install following pre-requisites:
- Service Pack 2 for WSS and SharePoint Server 2007
- April Cumulative Update for WSS and SharePoint 2007.
The April CU comes as hotfix – so you will need to register your email address and get the download link + password from your inbox.
Since its almost late for me, I think – I will continue the installation tomorrow, after downloading the package.
Check here for more details :
1. April CU : http://blogs.msdn.com/sharepoint/archive/2009/05/13/april-cumulative-update-packages-ready-for-download.aspx
2. Microsoft SharePoint Administration toolkit:
http://blogs.msdn.com/sharepoint/archive/2009/08/27/announcing-the-fourth-release-of-the-microsoft-sharepoint-administration-toolkit.aspx
-
-
English
Remember about critics to “stsadm –o copyappbincontent” to deploy SharePoint resource in my previous post here.
At the end of the post, I think that it should be “stsadm –o copyfarmappbincontent” instead.
Why?
Because the last will work in centralized deployment mode, same as solution deployment.
But what’s the secret? Why the standard copyappbincontent doesn’t work in farm configuration?
I’ll post in another article. But now, I have created the project in Codeplex. You can grab the code or download the binary here.
-
-
English
When you start to work with localization in SharePoint, I believe that you may end with one of Mikhail Dikov proposal here or here .
Partially I agree with his proposal, to leverage the resource deployment through the UI. However, his strategy may fail when you apply to server farm architecture with multiple Web Front End (WFE).
You have to go to every WFE, and activate/deactivate the feature before you can get it deployed in all WFE. The same concept as standard SharePoint’s stsadm command,
stsadm –o copyappbincontent
That command, instruct local SharePoint server to copy resources, sitemap etc. to web all application folder, except the Central Admin webapps.
And still we have big problem, that we have to run that command in every WFE.
I can say this is a big problem, because it against the concept of centralized deployment of WSP. Imagine, if you’re system administrator who wants to have WSP to automate distribution of artifact – and now you are facing a fact that since the WSP contains resources; you don’t have the centralized deployment concept anymore.
After doing
stsadm –o addsolution
stsadm –o deploysolution
in one of WFE - then you have to go through all WFE to execute
stsadm –o copyappbincontent
to deploy resources to webapps.
I know that some system administrator / production team, so we have to solve this problem. May be change it to stsadm –o copyfarmappbincontent , to perform appbincontent deployment in farm architecture.
-
-
English
Today, I’ve got an enquiries from one of our users, who could not configure their RSS WebParts. I know from the errors message, its related with proxy and authentication – but in fact he was trying to get feed from internal server.
So, what is the situation?
We have internal domain with suffix *.mib , however some of our internal server doesn’t have internal name or lies across the region. Those which lay on the other region are only accessible through *.com name, which then routed using VPN in our internal network.
Existing web.config, is a standard just like in Kit Kai blog, or Agusto blog.
Suspect
a. Authentication
All of our servers uses requires user authentication, which normally integrated into their domain account. However, when we deal with this kind of scenario, we may expect double-hop situation. Where users authentication need to be proxy to the next server. In our environment, we identified that this is not a problem since they all configured with KERBEROS.
b. Incorrect route
We know that the purpose of bypassing local proxy is to avoid RSS feed request to be routed through proxy. Having request through proxy could be cumbersome, since RSS webpart should handle authentication which is unsupported.
Hmm.. this could be the problem. Since the source RSS on other region is having *.com address; so in this case “bypassonlocal=true” doesn’t give any benefit.
The Fix
Fortunately there is one more section that we might overlooked. If we refer to MSDN in this link, we can specifically exclude any URLs from being proxied.
So, since I want exclude some internal *.mycompany.com from the proxy – I then modify the web.config into,
<configuration>
<system.net>
<defaultProxy>
<proxy proxyaddress="http://proxysvr.mib:8080" bypassonlocal="true" />
<bypasslist>
<add address="[a-z]+\.mycompany\.com" />
<add address="192\.168\..*" />
</bypasslist>
</defaultProxy>
</system.net>
</configuration>