Update on ISA Server 2004 Deployment Kits:
Heads Up on SharePoint Portal Server and Branch Offices
By Thomas W Shinder M.D., MVP
We’ve been working hard on updating the ISA Server Deployment Kits over the last few months. I’m happy to report that the ISA Server 2004 VPN and ISA Server 2004/Exchange Deployment Kits have been finished. The ISA Server 2004 Branch Office Deployment Kit is in development now and we expect to have those ready for you this month. The ISA Server 2000 Deployment Kits have been enormously popular, so it would have been a crime not to update them!
There are a couple of things I’d like to ask everyone in the ISAServer.org community about before we get to updating the Branch Office Kit and the SharePoint Portal Server kit.
First, the Branch Office kit. If you haven’t seen the ISA Server 2000 Branch Office Kit, check it out at http://isaserver.org/articles/bokit.html. It includes a number of scenarios related to branch office/main office connectivity using ISA Server 2000 firewalls. If you have already read the ISA Server 2000 Branch Office kit, great! I hope it answered your questions about branch office connectivity and you’ve got things up and running.
For the ISA Server 2004 Branch Office Kit, are there any scenarios you would be interested in that aren’t covered in the ISA Server 2000 Branch Office Kit documents? If so, I’d like to know so that we can get those subjects in covered in step by step detail. Any issue you can think of regarding connecting branch offices to the main office using ISA Server 2004 is fair game! Just send me a note at email@example.com or firstname.lastname@example.org and I’ll make sure to do whatever I can to get your desired scenario covered in the kit.
Second, the ISA Server 2004 SharePoint Portal Server Deployment Kit. I know that a great number of you have benefited from the ISA Server 2000 SharePoint Portal Server Kit (http://isaserver.org/articles/sharepointkit.html) and are using ISA Server 2000 firewalls and Web Proxies to publish your SharePoint Portal Server sites. If you’re using ISA Server 2000 to publish your SharePoint Portal Server sites, then I want to talk to you. We haven’t decided yet if we’ll update that kit, and the decision to do so is up to you.
What we need to know in order to make a decision about updating the kit is included in the following short questionnaire. If you just copy and paste the below into an e-mail message, along with your answers, I’ll get back to you personally and discuss your observations and needs in more detail:
Copy below this line:
- Are you using ISA Server 2000 firewalls or Web proxy servers to enable remote access to your current SharePoint Portal Server installation? (Yes/No)
- Are you using ISA Server 2000 to provide secure remote access to your SharePoint sites to meet legal requirements, such as the Sarbanes-Oxley or HIPPA regulations (or your local equivalents? (Yes/No)
- What SharePoint Portal Server features are you providing users remote access to?
- What SharePoint Portal Server features would you like to provide remote access to, but you are not able to make them work?
Copy above this line
After getting your answers, I’ll write back to you for more information. SharePoint Portal Server publishing is extremely popular, and we want to make sure that we provide the right information, and enough information, to get your remote access SharePoint Portal Server remote access solution working the way you want it to.
I hope you enjoyed this article and found something in it that you can apply to your own network. If you have any questions on anything I discussed in this article, head on over to http://forums.isaserver.org/ultimatebb.cgi?ubb=get_topic;f=2;t=012850 and post a message. I’ll be informed of your post and will answer your questions ASAP. Thanks! –Tom
If you would like us to email you when Tom Shinder releases another article on ISAserver.org, subscribe to our ‘Real-Time Article Update’ by clicking here. Please note that we do NOT sell or rent the email addresses belonging to our subscribers; we respect your privacy