1. Deploying And Managing Microsoft ® FrontPage ® 98- Based Web Sites On Internet Information Server

2. Objectives Explain extended functionality provided by Server Extensions Explain extended functionality provided by Server Extensions Provide a clear picture of the Extensions architecture Provide a clear picture of the Extensions architecture Understand choices for deployment of FrontPage and Extensions Understand choices for deployment of FrontPage and Extensions Explain how to install, configure, and manage the Extensions on Internet Information Server Explain how to install, configure, and manage the Extensions on Internet Information Server Outline security mechanism and clear up security misunderstandings Outline security mechanism and clear up security misunderstandings

3. Agenda Server Extensions Tasks Server Extensions Tasks Server Extensions Architecture Server Extensions Architecture Deploying Deploying Security Security Site Management Site Management Integration with Internet Information Server technologies Integration with Internet Information Server technologies

4. Server Extensions Tasks “Impedance match” between client and server “Impedance match” between client and server Platform-independent protocol for authoring, management, and administrative operations Platform-independent protocol for authoring, management, and administrative operations Multiuser and remote authoring Multiuser and remote authoring Convenient packaging for server-side functionality Convenient packaging for server-side functionality Not required for 95% Browse- time functionality Not required for 95% Browse- time functionality

5. Server Extensions Tasks Authoring and managing Authoring and managing  Create and save pages  File management: move, copy, del  Maintain hyperlink integrity  Copying and publishing Webs  Automatic Navigation Bars and Themes Metadata maintenance Metadata maintenance  Hyperlink map  Create date, Created by, custom

6. Server Extensions Tasks Administering - Security Administering - Security  Users and Permissions Browse-time Web functionality Browse-time Web functionality  Form Handlers: e-mail, results file  Search Form  Discussion Web 95% of browse-time functionality does not require Server Extensions! 95% of browse-time functionality does not require Server Extensions!

7. HTTP Web server IIS IIS PWS PWS Apache Apache Netscape Netscape ISAPIorCGI FrontPage Architecture FrontPageExtensions Author.dll Admin.dll Shtml.dll EditorExplorer

8. Deployment Issues Authoring scenarios Authoring scenarios Content structure Content structure Installation Installation

9. Web Authoring And Publishing Scenarios Single author Single author  Local authoring  Remote publishing to Web server  Server Extensions NOT installed: FTP  Server Extensions INSTALLED

10. Local Authoring And Testing Extensions on local machine Extensions on local machine  Local authoring and Web management  Local testing for browse-time components  Optional: Lightweight FrontPage- based personal Web in workgroup

11. Web Authoring - Local Test & Preview Browser HTTP Local Workstation Extensions Personal Web Server Hard Disk HTTP Author and Manage Browser Optional: Workgroup users browse your lightweight personal Web HTTP

12. Local Authoring, Remote Publishing Extensions on local machine Extensions on local machine  Local authoring  Local FrontPage component testing Publish to remote Web Server Publish to remote Web Server  Works best with Server Extensions  Extensions not required on remote Web Server: Publish via FTP  No Browse-time FrontPage components without Extensions

13. Extensions on remote Web server Extensions on remote Web server  Smart publishing receptor  Additional 5% enhanced browse-time functionality  Save-results form to file and e-mail  Search  Hit counter  Discussion group Local Authoring, Remote Publishing

14. Remote Publishing & Authoring Author Internet Information Server Intranet or WPP Web Server Publish via FTP Local Workstation Extensions Extensions Personal Web Server Hard Disk Server Machine Hard Disk FULL browse- time functionality Browse Browser Publish via HTTP (NO browse- time functionality) Browse Browser Incremental Authoring & Publishing

15. Web Authoring And Publishing Scenarios Team authoring Team authoring  Author local, publish to shared server  Extensions not required but recommended  Author against shared server  Extensions on shared server  No publishing - live authoring

16. Team Authoring Extensions recommended on shared server Extensions recommended on shared server  Live authoring and management over network or Internet  Workgroup functionality: Conflicts, Todo  Browse-time FrontPage components  Version control with Visual SourceSafe ™ Extensions on workstation Extensions on workstation  Useful for offline authoring and testing  Not required

17. Shared Server Model HTTP Extensions Authoring or Staging Server (IIS) Server Machine Hard Disk Production Intranet or ISP Web Server Internet Information Server Extensions(optional) Server Machine Hard Disk Workstations - FrontPage Clients Optional: Propagate to production server

18. Team Authoring Options: Options:  Staging server - prop to production server  Validation  Security  Version Control - Check-in/Check-out  Review process

19. Deploying: Content Structure FrontPage-based Web concept FrontPage-based Web concept Web usage scenarios and storage layout Web usage scenarios and storage layout Implementation on Internet Information Server Implementation on Internet Information Server

20. FrontPage-Based Webs All HTML, images, and other files for a Web site All HTML, images, and other files for a Web site Subfolders available Subfolders available Scope of FrontPage: Scope of FrontPage:  Authoring  File and link management  Security  Publishing  FrontPage component functionality

21. Usage Scenarios: WWW Per-user subwebs (a la AOL, GeoCities) Per-user subwebs (a la AOL, GeoCities)  www.isp.com/~george  Large number hosted on one machine Virtual server per user Virtual server per user  www.billg.com  Usually several to many per machine Dedicated server per organization Dedicated server per organization  www.arcadiabay.com

22. Hard Drive Storage Web Structure C:\InetPub\wwwroot default.htm \scripts signup.asp Root Web: http://www.ISP.com WWW Folder Structure Virtual Server Contoso Pharmaceuticals Web: http://www.contoso.com \Contoso default.htm \Contoso default.htm Virtual Server Arcadia Bay WWW Presence: http://www.arcadiabay.com \ArcadiaBay default.htm \products product1.htm \ArcadiaBay default.htm \products product1.htm

23. Usage Scenarios: Intranet Server per project/department Server per project/department  http://arcadianet  Root area maintained by Webmasters Project/Department subwebs Project/Department subwebs  arcadianet/HR  arcadianet/Finance  Subwebs for workgroups divide authoring responsibility and permissions

24. Hard Drive Storage Web Structure C:\InetPub\wwwroot default.htm companylogo.gif \scripts search.asp Root Web: http://arcadianet/ Index of departmentsIndex of departments Global scriptsGlobal scripts Intranet Folder Structure Finance Product Group: http://arcadianet/Finweb C:\InetPub\wwwroot\finweb C:\InetPub\wwwroot\finweb default.htm default.htm Human Resources subweb: http://arcadianet/HR C:\InetPub\wwwroot\hr default.htm \policies hrpolicy.doc C:\InetPub\wwwroot\hr default.htm \policies hrpolicy.doc

25. Root Webs And Subwebs Root Webs Root Webs  One per virtual server Subwebs Subwebs  Many subwebs per virtual server No functional difference for user browsing or authoring Web No functional difference for user browsing or authoring Web

26. Root Web One root Web per virtual server One root Web per virtual server Content folder defined by the virtual root Content folder defined by the virtual root  C:\InetPub\wwwroot  Other arbitrary locations for multihosted servers Access via http://www.server.com Access via http://www.server.com

27. subwebs Stored as a sub-folder of root Web content folder Stored as a sub-folder of root Web content folder  Access as http://server/subwebname C:\InetPub\wwwroot default.htm Root Web: http://arcadianet Arcadia Bay Sales subweb: http://arcadianet/sales C:\InetPub\wwwroot\sales default.htm \promotions

28. Subwebs Logically excluded from root Web authoring space Logically excluded from root Web authoring space Nested subwebs: Extensions do not allow Nested subwebs: Extensions do not allow Can inherit permissions from root Web Can inherit permissions from root Web Number of subwebs: No hard-coded limit Number of subwebs: No hard-coded limit

29. Deployment: Installation Get the extensions Get the extensions Basic installation Basic installation Configure servers Configure servers Upgrade issues Upgrade issues Finishing details Finishing details

30. Get The Extensions FrontPage client product FrontPage client product  Client setup installs Extensions locally Windows NT ® 4.0 Option Pack, Internet Information Server 4.0 Windows NT ® 4.0 Option Pack, Internet Information Server 4.0  Integrated Extensions setup Windows ® and UNIX Extensions setup kits Windows ® and UNIX Extensions setup kits  http://microsoft.com/frontpage/wpp/

31. Basic Installation Get the FrontPage 98 Server Extensions Resource Kit (SERK) Get the FrontPage 98 Server Extensions Resource Kit (SERK)  At minimum read Security and Installation sections Run Installer to copy Extensions to HD Run Installer to copy Extensions to HD Create virtual servers Create virtual servers Configure each virtual server Configure each virtual server

32. Configuring Servers With Extensions Setup automatically configures single-hosted servers Setup automatically configures single-hosted servers If multihosted, or adding new virtual server, use: If multihosted, or adding new virtual server, use:  FrontPage Server Administrator  Remote HTML Administration Forms Create subwebs with FrontPage Explorer Create subwebs with FrontPage Explorer

33. Upgrade Issues When required When required  New version of extensions for each client version  Intermediate patches and updates Compatibility Compatibility  New client with old extensions  New extensions with old client Setup automatically upgrades Setup automatically upgrades May reparse content May reparse content

34. FrontPage 98 Server Extensions Improvements No memory leaks No memory leaks Quicker to install Quicker to install New remote HTML Administration Forms New remote HTML Administration Forms Better scalability and robustness Better scalability and robustness  Open Web not a limitation

35. FrontPage 98 Scalability No hard-coded subweb or file limits No hard-coded subweb or file limits  May hit Internet Information Server limits Possible scalability limits Possible scalability limits  Recalculate hyperlinks - linear scaling  Saving change to shared border on many- paged Web (~ 2 pages / second) Break up content into different subwebs Break up content into different subwebs

36. Finishing Details Web-specific options in FRONTPG.INI Web-specific options in FRONTPG.INI Visual SourceSafe integration for Web Visual SourceSafe integration for Web E-mail transport E-mail transport Import existing documents Import existing documents HTML Administration Forms HTML Administration Forms Security Security

37. Agenda Server Extensions Tasks Server Extensions Tasks Server Extensions Architecture Server Extensions Architecture Deploying Deploying Security Security Site Management Site Management Integration with Internet Information Server technologies Integration with Internet Information Server technologies

38. Security FrontPage Security Model FrontPage Security Model Implementation with Internet Information Server Implementation with Internet Information Server Security Management Strategies Security Management Strategies  Custom ACLs

39. FrontPage Security Model Uses Web server security system Uses Web server security system  No homegrown FrontPage security mechanism Permissions groups Permissions groups  Users: Browse Web content  Authors: Manipulate files and directories  Administrators: Create new subwebs, change permissions Permissions are cumulative Permissions are cumulative

40. FrontPage And Internet Information Server Security Process Internet Information Server authenticates user Internet Information Server authenticates user  Basic, Windows NT Challenge/Response, DPA Internet Information Server Impersonates Windows NT user account Internet Information Server Impersonates Windows NT user account FP sends HTTP request to one of three DLLs: FP sends HTTP request to one of three DLLs:  Administer: admin.dll  Author: author.dll  Browse: shtml.dll Internet Information Server grants/denies access based on ACL of target DLL file Internet Information Server grants/denies access based on ACL of target DLL file FP reads/writes content files based on request FP reads/writes content files based on request

41. FrontPage ACL Management FP manages FP DLL ACLs FP manages FP DLL ACLs  Maintain admin/author/browse  Protect FP configuration info: _vti_* FP manages content ACLs FP manages content ACLs  Conservative settings for max security  Authors/Administrators get read, write, delete (RWD)  Browsers get read (R) See SERK for specific list See SERK for specific list

42. Permissions Management Strategies Permissions managed by FrontPage Permissions managed by FrontPage  FP Admins use Tools | Permissions command  FP controls content ACLs Best Practices Best Practices  Separate subwebs  finer control  Use Windows NT Groups for easiest maintenance

43. Permissions Management Strategies Staging server/Production server Staging server/Production server  FrontPage manages staging server security  Production server uses custom settings Manual/Custom management Manual/Custom management

44. Custom ACLs Use FP one time to add Windows NT groups for Admins/Authors/Browsers Use FP one time to add Windows NT groups for Admins/Authors/Browsers Disable FrontPage security Disable FrontPage security  FP Tools/Permissions overwrites custom ACLs  No FP Administrators Manage ACLs with Windows Shell, cacls.exe Manage ACLs with Windows Shell, cacls.exe

45. Custom ACL Cautions Windows shell replaces ACLs, not merge Windows shell replaces ACLs, not merge Use Recursive Replace with care Use Recursive Replace with care Do not overwrite key ACLs on Do not overwrite key ACLs on  FrontPage DLLs  _vti_* directories Understand Internet Information Server Anonymous account vs. EVERYONE Understand Internet Information Server Anonymous account vs. EVERYONE

46. Custom ACL Downsides Can easily get to state where: Can easily get to state where:  Security worse than default FrontPage configuration  FrontPage doesn’t work Recovery steps: Recovery steps:  Use Check and Fix command  Uninstall Server Extensions, Fix ACLs, then reinstall

47. Agenda Server Extensions Tasks Server Extensions Tasks Server Extensions Architecture Server Extensions Architecture Deploying Deploying Security Security Site Management Site Management Integration with Internet Information Server technologies Integration with Internet Information Server technologies

48. FrontPage Server Extensions Related Tools FrontPage Server Administrator FrontPage Server Administrator  fpsrvwin.exe Command line server administrator Command line server administrator  fpsrvadm.exe Remote administration HTML forms Remote administration HTML forms

49. Maintenance Of Server Extensions “Check & Fix Web” feature in Server Administrator “Check & Fix Web” feature in Server Administrator Reinstall Server Extensions to correct corrupted Extensions Reinstall Server Extensions to correct corrupted Extensions Enable/disable authoring Enable/disable authoring Files to know Files to know  frontpg.ini - various FrontPage settings

50. Recalcing Webs Recalcing Web reparses each page to repair or rebuild: Recalcing Web reparses each page to repair or rebuild:  Link map, WAIS index, Navigation Bars, FrontPage Components, Shared Borders, etc. Normally not necessary, unless working outside of FrontPage Normally not necessary, unless working outside of FrontPage  File System, FTP Linear scaling, possibly high server load Linear scaling, possibly high server load

51. Agenda Server Extensions Tasks Server Extensions Tasks Server Extensions Architecture Server Extensions Architecture Deploying Deploying Security Security Site Management Site Management Integration with Internet Information Server technologies Integration with Internet Information Server technologies

52. Active Server Pages FrontPage 98 Server Extensions don’t corrupt ASP FrontPage 98 Server Extensions don’t corrupt ASP  Safe to store ASP documents Opening ASP in Editor may corrupt Opening ASP in Editor may corrupt  Partial HTML tags, unclosed HTML tags Workarounds Workarounds  Encapsulate ASP in WebBot ® Component meta-tags  DTC, WebBot Component wrapper

53. Other Technologies Index Server Index Server  Possible search engines  Index Server if installed  Built-in WAIS  Builds IDQ files automatically Forms to SMTP e-mail Forms to SMTP e-mail

54. Version Control With Microsoft Visual SourceSafe FrontPage 98 Visual InterDev FrontPage 97 Web staging server HTTP LANconnection VSS repository IIS Extensions OLE Automation

55. The FrontPage 98 SERK Definitive source for in-depth Server Extensions info for Windows and UNIX Definitive source for in-depth Server Extensions info for Windows and UNIX  Security, Installation, and Administration  Troubleshooting, Config Settings, more Where: Where:  FrontPage 98 CD in \SERK directory  http://microsoft.com/frontpage/wpp/serk Read Security and Installation sections Read Security and Installation sections

56. Other FrontPage Resources Server Extensions Web site Server Extensions Web site  http://microsoft.com/frontpage/wpp FrontPage SDK FrontPage SDK  FrontPage 98 CD in \SDK directory Newsgroups Newsgroups