December 2007 - Posts
They have finally finished the new web site. Check it out and see the evolution of the ladies. KKI is growing and maturing. May the founders continue to smile on the achievements you make in the building of the organization.
Welcome to the National Website of Krimson Kourts Incorporated National Service Organization
For those who are upgrading to Outlook 2007 and are still using [wssv2] then be aware that importing contacts and address book functionality will not work. Either keep the old version of Outlook on your machine (I have not tested this) or follow the steps outlined in the linked KB article.
Error message when you try to add users or import contacts from Outlook 2007 to a Windows SharePoint Services V2 Web site: "You must have an Address Book compatible with Windows SharePoint Services"
If you want to know what this web part does, this MVP gives a good description...
If you wish to use the custom list route, create a custom list that contains the Title (always created by default), a field to hold URLs (I call it URL) and finally a field that allows choices that will be used to filter the entries.
I need to... - ShareBlog
For those using an [Exchange] server over DSL or small businesses that are using Exchange I found an interesting problem.
By default [Exchange] and the Windows SMTP service only supports explicit SSL or TLS encryption of outbound SMTP traffic (the history is outlined in this TechNet article). That being the case the problem that you have (and I have run into) is the fact that many ISPs are transitioning to the implicit SMTPS encryption for outbound connections. This means that traffic for [SMTP] has to flow over port 465. If you are using your ISP's outbound mail servers (for those on Dynamic DSL lines, you are blocked from direct sending by several domains such as yahoo.com, hotmail.com, and several other corporate ones as well) you must authenticate (easy to setup with a custom send connector for the domain you specify) and send the [SMTP] over port 465.
So here's the trick. If you have ISA Server, you have to be a bit innovative (I did not find a direct reference to do this, but inferred the idea from the linked discussion). Basically you need to "publish" the ISP's email server to your internal clients. By doing this step you create a publishing rule for internal clients to connect to that mail server. Next what you want to do is change the rule so that it listens on port 25 for traffic coming from your internal Exchange server/network. The outbound traffic to the ISP server then transitions to the 465 port.
The implicit SSL then works as expected and [Exchange] thinks it is talking on port 25 while the ISP gets the 465 port it wants. What donned on me while trying to trouble shoot and what the linked discussion talks about is the fact that publishing does not have to just be external to internal. It can actually go the opposite direction. Just be sure to specify the proper server and address and you should be able to change the standard port 25 to what ever port you define within the ISA protocols.
If you have another firewall, sorry I don't have a guide for you. But consider the steps above and modify them according to what your firewall requires for publishing and port forwarding.
Global Port Redirection
If you ever need some guidance on configuring the Virtual networks on your [VirtualPC] or [VirtualServer] configurations, this search will return all the ones relating to the Loopback configuration. I usually see a lot of confusion on this topic.
Live Search: ("Virtual PC" "Virtual Server") Loopback adapter configuration
The end user training is finally available. For SharePoint Technology 2003, it was a CHM file that you could download. Now they have two versions. One that can be saved to a portal and another that can be saved to a desktop. For all the classes I have worked with, this can help you train your end users.
Get SharePoint training on your desktop - SharePoint Server - Microsoft Office Online
This means it is almost time to purchase the new Mustang Shelby Cobra I've been eying. Can't wait to see SYNC working in that bad boy...
Also Mass Effect would be a good game to try out.
Microsoft's Holiday Preview | Larry Larsen | Channel 10
To do remote access for your Firewall with Windows Home Server, here are the required ports you need to make available.
| You can use the Router Configuration Wizard from the Console under the Settings ->Remote Access tab. This will create your FREE Windows Live Domain, automatically configure your router to port forward the correct ports, and update Windows Live Domain with your IP address. If you need to manually configure your router, you will need to forward these ports on your router: - 443 TCP
- 4125 TCP
- 80 TCP (optional, you can use https://<ip or domain name>/remote instead of http://<ip or domain name>/remote)
Using HTTPS:// will bring you to the log on screen instead of http:// which will bring you to the home page. This can be a work around for port 80 being blocked.
Windows Home Server Team |
So in the case of ISA server you will probably need to publish the server with the above ports and listen for the particular host name. That will allow you to forward to your Home Server and access your machines remotely. If this works for you let me know. I have not had the chance to try this in my environment to verify everything (don't have a home server yet).
Remote Access: What ports do I need to forward from my broadband router/firewall to my home server for remote access? - Windows Home Server