Novell Home

Installing iFolder v2.1.3 on Windows 2003

Novell Cool Solutions: Tip
By Roy Lopez

Digg This - Slashdot This

Posted: 12 Jan 2006
 

Making iFolder v2.1.3 installation on Windows 2003 less aggravating...

While Novell is to be commended for making iFolder available on Windows Server, and for allowing it to be used with Active Directory instead of eDirectory (the better choice), it has not completely documented either in the documentation or in the Novell Technical Information Documents on how to properly prepare your Windows Server without much aggravation on the part of the implementer. Recently finding myself faced with this challenge I eventually found all of the right material to make this integration as easy as possible. Interesting enough, the Microsoft support site, in particular their IIS Resource Center site had information that allowed me to achieve the easy integration that I thought this was suppose to be, albeit after some more searching.

So, I submit this tip because it seems to me that this is a great way to demonstrate Novell's openness and willingness to support its' products on other than its' native platform, or even on its' directory. Which is why I believe that this integration really requires minimizing the potential aggravation to an implementer, else it will become just another easy excuse for not using a Novell product in their Windows environment. Now while I am not a Windows expert, or Novell Technical Support, I invite any interested party to submit feedback directly to me so that all can benefit from our collective experiences.

For example, *does anybody know where to get iFolder v2.1.6? While it is mentioned in the iFolder 2.1 documentation but I cannot find it on any of the publicly available sites.

Solution

The bottom line to do this integration is the following:

  1. Install Windows 2003 Server – Standard or Enterprise;
  2. Update Windows 2003 Server to the latest support pack (we did sp1);
  3. Make sure that your server name dns name is either in DNS or your host file;
  4. Check the Windows Firewall and set it to allow inbound requests to port 80 and 443;
  5. Install Internet Information Services from the Windows CD;
  6. To Install Certificate Services, access Control Panel Add Programs, Windows components, this will enable Active Server pages for you, let it;
  7. Follow the instructions in the How to Implement SSL in IIS listed below:

    You should check the WebSite to require SSL so as to check that you can enable, and disable this functionality – you really are in the drivers' seat now–and are ready to install iFolder, and it should now install as Novell intended it too;
  8. Access the iFolder v2.1.3 on Windows 2003 Technical Information Doc for both the v2.1.3 code, and its? instructions;
  9. Once it unzipped access the appropriate language directory and run the iFolder setup;
  10. You should be the administrator account, specify a DNS name for your server, and remember that we are talking LDAP, so commas instead of periods;

Useful Technical Information Resources

Regarding preparing your Windows 2003 (or 2002) Server

How To Implement SSL in IIS http://support.microsoft.com/kb/299875/en-us

How To Troubleshoot a Web Server in Windows 2003--. http://support.microsoft.com/kb/323358/

Regarding installing and configuring iFolder 2.1 on a Windows Server, using AD:

iFolder 2.1.3 for Windows 2003 -- This was the latest version of the code that we used http://support.novell.com/techcenter/search/search.do?cmd=displayKC&docType=kc&externalId=InfoDocument-2969743html&sliceId=&dialogID=3742334

Review the iFolder 2.1 docs for installing and configuring on Windows 2003 http://www.novell.com/documentation/ifolder21/

Environment:

  • We did an English only installation, so did not test against non-English implementations.
  • We used Windows 2003 Enterprise, so did not test against Small Business or Standard.
  • We updated to Windows 2003 sp1, and the latest available critical updates.
  • We did not have to require SSL for the iFolderServer page to work.
  • We did not have to add the mime type (.* application/octet-string) for this to work.
  • We used the iFolder v2.1.3 release.


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell