Archive for July, 2007

Adding an e-mail account to a T-Mobile Sidekick 3

Tuesday, July 24th, 2007

Adding POP3 or IMAP accounts

To add POP3 or IMAP accounts, perform the following steps:

1. At Jump screen, scroll to and select Email.

2. Press the Menu key.

3. Scroll to and select Settings.

4. Scroll to and select Accounts.

5. Press the Menu key.

6. Scroll to and select New Account.

7. At Account, type or select the following information:

At Protocol, select the protocol used by your mail server. It is recommend that you select the auto-detect setting.
At Mail Server, type the mail server information. If this field does not auto-fill after selecting the protocol, contact your e-mail provider.
At Port, do not change the number unless directed by your e-mail provider.
At Username and Password, type the username and password for your e-mail account.
At Email Folder, select the folder where your incoming e-mail will be delivered.

8. Select Create to save.

Note that even if you select IMAP and use port 143, it will still treat the mailbox as though it were POP. Messages will not be marked as read/not read when you look at them on the handheld.

Connecting Windows Vista to a Mac OS X Server Running Open Directory

Friday, July 13th, 2007

- Click Start
- Click Control Panel
- Click System and Maintenance
- Click Administrative Tools
- Double-Click Local Security Policy
- In the left pane, click the triangle next to Local Policy
- In the left pane, click Security Options
- In the right pane near the bottom, double-click “Network security: LAN
manager authentication level”
- Click the drop-down box, and click “Send LM & NTLM – use NTLMv2 session
security if negotiated”
- Click OK
- Restart the computer

Importing Modules Into a FileMaker 1 File Solution

Saturday, July 7th, 2007

There is clearly a process that should be followed when combining multiple modules [files] into a single file solution. Without careful adherence to these guidelines it is easy to find that scripts and layouts (layout objects) will to break and therefore you end up starting over or trying to fix all of the errors that occur. Hopefully after reading this article you can save time in the front end and a lot of grief along the way.

Step 1: Make sure all Global Elements are in place.
Having a good handle on how the navigation and global elements and the discrepancies between your two solutions will keep you from scratching your head later on. Add any fields and global elements that you think will be necessary before continuing.

Step 2: Importing Tables and TOG’s and File References-
The most important step is to import all related tables. In the new solution make sure that none of the existing tables have the exact name as a table you plan to import. Rename any existing tables in the new solution BEFORE importing the old tables. Once they have been renamed you’ve setup a clean consistent naming method that won’t create any field missing links later on.

Depending on your method of importing the table, you may need to worry about the data. If this is a Navigation module or similar, don’t delete the records after import and use the import records from file as table command. Make sure you update your auto-enter serials.

Check that all the necessary file references exist. It is easier to make them first before creating any TOGs that need these relationships.

Recreate alll TOG’s EXACTLY as they are in the old solution. The names must be consistent to avoid scripts and layouts to break along the way.

Go through all field definitions and fix any broken calculations. Keep track of any that you can’t fix and need to be fixed later. Documentation is your friend!

Step 3: Recreate all Custom Functions, Privilege Sets & Custom Menus & Value Lists
Recreate any Custom Functions in the old solution that do not already exist in the new solution. (You must do this before scripts are imported. You may need to fix and field definition calculations at this time.) All these have to be done by hand because FMP won’t allow cutting and pasting of custom functions and value lists. Privilege Sets and Custom Menus are not as necessary unless you have a lot of scripting that depends on them. If so, do this now! Field Layout Objects are dependent on Value Lists so do these now.

Step 4: Make Blank Layouts-
Make blank layouts with the exact same names as the ones you wish to import. (This will save any scripts that use the go to layout command and buttons that also would use the go to layout command.)

Step 5: Import Scripts-
The best way to do this is first to make a print out of the names of all the scripts in the old solution. Go through and make sure you have a general understanding of each one of the scripts that you plan to import. (This way if something breaks you will know where the error occurs. )

Import the scripts. Some renaming may be necessary but DON’T rename them yet! You haven’t imported the layouts yet and many objects are dependent upon these names. Just make notes on the scripts you wish to change names.

Review the import log file and fix any errors you do encounter in the scripts. This information is golden. If the errors are too numerous, delete the imported scripts, fix the issues and reimport the scripts.

Step 6: Fix Custom Menus that use scripts-
This is a which comes first the chicken or the egg situation. If all of your custom menus are dependent on scripts, create the scripts first, and then create the custom menus. Either way you may have either scripts steps that load a custom menu or unknown scripts in your custom menu sets. You choose the best approach.

Step 7: Layout Objects-
Now is the time you can recreate the layout objects. Select ALL and copy and then paste the objects on the blank layouts you created earlier. Hopefully if you’ve followed all the above steps in order you will be left with minimal if not no table missing and field missing objects. [Although, FMP best practices state that copy and pasting graphic objects into a layout as opposed to using the FMP menu command of “Insert...”, is, according to FMI, the leading cause of corruption in FMP systems - It is always best to follow best practices, but not always practical or profitable.]

Remember the global objects you created earlier? This will be the time you’ll find out if you’ve missed one! Sometimes it might be easier to go back and recreate the missing objects first and then redo step 6. Weigh your options when you begin clicking through the layouts.

Step 8 & 9: Test, Debug & Rename:
Click on all buttons, go under the hood and look for buttons with unknown scripts and missing parameters. Just find out what is broken. Make notes as you test.

AFTER you’ve tested everything NOW you can go back and change the names of your TOG’s, your fields, your scripts, and everything else you had the urge to change but shouldn’t have.

And your solution should be good to go!

Final note: DO NOT EVER SUCCUMB to the urge of changing names as you go. No matter how you justify it, it will break something during the import process Guaranteed.

Distributed Computing for Good

Friday, July 6th, 2007

Most screen savers just waste power. Might as well just put your computer to sleep. But if you want to use a screen saver and you want to do something good for humanity then check out one of these: – Join more than 300,000 other computing nodes and dedicate your computing power to finding new AIDS treatments – Improve climate prediction models with the University of Oxford – Help George Woltman be the first to find a 10 million-digit prime – Test Einstein’s theory of gravitational waves

Using Outlook Remotely with RPC over HTTPS

Friday, July 6th, 2007

Setting up RPC over HTTPS is different than setting up Entourage over HTTP/S. First, an overview of what HTTPS is. HTTPS is the secure form of HTTP, it stands for HyperText Transfer Protocol Secure. This means that you will need an SSL certificate for connection between Outlook and Exchange. RPC is what Outlook uses to synchronize special information over from Exchange. RPC stands for Remote Procedure Call, and is the special programming routine that allows the application (Outlook) to connect with Exchange via OWA.

Now that we’ve established what RPC over HTTPS is, an outline will follow of how to connect Outlook to Exchange using RPC over HTTPS on Windows 2003 Small Business Server.


Small business server comes with many things already installed and ready for use right out of the box for a company. Two of these things are Exchange and Remote Web Workplace. Remote Web Workplace seems to be an idea made by Microsoft so that an Administrator could remote into their server via HTTP/S, and from there can use many tools in Remote Web Workplace to administer the entire network infrastructure via the Small Business server.

Check List:
1. Are you using Small Business Server 2003?
2. Is Exchange functioning and setup correctly?
3. Do you have an SSL certificate?
4. Are ports 80 and 443 open (and 3389 if you’re doing this remotely)?
5. Do you know the NetBios name of the server (right mouse click My Computer and check the computer name)?
6. Do you have Outlook (preferably 2003)?
7. Are the client workstations that need remote access updated with SP2 for XP?

If you have this, then you’re ready to rock.

Getting it All to Work Together

1. Make Them a Member of Remote Web Workplace

Log in as Administrator to the Small Business server and open up Active Directory Users and Computers. Locate the users you want to have access (or create a security group) and add the group or user to the following group called, “Remote Web Workplace”.

NOTE: You may not see this group as a security group in Active Directory, but if you type in the name and press the “Check” button, it should underline itself. You have now confirmed that this is a valid Security Group.

2. Get The Facts

With the new user you created, login to This is the Remote Web Workplace that you are logging into. You should be greeted with a login. Use the credentials for the user (or pick a user from the security group) that is now a member of “Remote Web Workplace”. You should be able to log in. If you cannot, log in to Remote Web Workplace, log in as Administrator and see if you can log in. If you can log in with the Administrator account, check your settings that you’ve applied to the security group, or user, and ensure that they are indeed members of “Remote Web Workplace”.

Once you have logged in, to the right, there should be a link called “Configure your computer to use Outlook via the Internet”, click on it, and it will outline steps that are pretty darn close to what you should setup in Outlook. It’s basically a help file, but it will give you almost exactly what you will need to use RPC over HTTPS. Just in case, I will also outline the steps here that the link will post.

NOTE: It is important that your users can log in to Remote Web Workplace with the users that need access to RPC over HTTPS. If they cannot log in to here, you will NOT be able to user RPC over HTTPS.

3. Configure or Reconfigure the SSL Certificate

When you log in to Remote Web Workplace via HTTPS, you should be greeted with a pop-up that asks if you want to accept the SSL cert. Check the SSL certificate and MAKE SURE THAT THE WEBSITE NAME OF THE CERT MATCHES THE WEBSITE.

If it does, then log in from each computer that needs RPC over HTTPS and install the certificate from Remote Web Workplace by clicking on View Certificate, and then Install Certificate. You can double-check that the certificate is installed by opening up MMC, go to Certificates, pull up the one for User Certificates, and look for one named with the server or domain name as a Trusted Root. Again, make sure that the cert’s name (not the CA issuer) is called by the MX record name (or predetermined Exchange website name) and NOT THE SERVER NAME. After you install the certificate, close Internet Explorer, and reopen it, and log in to Remote Web Workplace. If you are prompted to accept the certificate again, something is wrong with the certificate, and you will need to create a new one.

If the certificate doesn’t match the Exchange website name or the certificate saved keeps prompting you to accept it, you will need to create a new certificate. You can do this by the following:
1. Download IIS 6.0 Resource Kit Tools, available from:

2. Run the application, and install SelfSSL
3. Click on Start -> All Programs -> IIS 6.0 Resource Kit -> SelfSSl
4. In the Command Prompt type the following:

selfssl /T /N:CN=

NOTE: should be your Exchange website name, ie., (without the less-than and greater-than signs).

5. Type “y” to replace the SSL settings for site 1.
6. Log in to Remote Web Workplace again, and display the certificate. Ensure it is now called what it is supposed to (HINT: Before you view the certificate there should be a green check mark for “Certificate matches website name”). Install the cert, close IE, and retest. You should not longer be prompted to accept the certificate.

NOTE: This is important because if the certificate does not match the Exchange website name the connection will FAIL. You will either get a “server not available error” or other unusual errors.

4. Configure Outlook (a.k.a, It’s all Downhill from Here)

NOTE: This is available in Remote Web Workplace under the link: “Configure your computer to use Outlook via the Internet”

1. Go to Control Panel -> Mail -> Profiles and create a new Profile
2. With the new profile create an e-mail account, make sure to choose Exchange.
a. For the server name put the NetBIOS name, NOT THE WEB NAME.
b. For the user name, put in the username of the user.

NOTE: Do not hit, “Check” it will not work.

c. Click on the “More Settings” button.
d. Click the Connection Tab.
i. Checkmark the box that says “Connect to my Exchange mailbox using HTTP”
ii. Press the Exchange Proxy Settings Button
1. For https:// put in the website name that we’ve been getting the certificate ready for.
2. Put a check mark for “Connect using SSL only”
3. Put a check mark for “Mutually authenticate the session when connecting with SSL”.
4. For “Principal name for proxy server:” put the following:
5. Put a check mark for “On fast networks…” and “On slow networks…”
6. For “Proxy authentication settings” change it to “Basic Authentication”
3. Press OK a bunch of times, Next, and then Finish.
4. Make sure that this profile is set to “Always use this Profile”
5. Save your settings
6. Test your settings, and if you’ve done everything right, you should be prompted for your credentials. After you have been authenticated, you should now start receiving e-mail, and be able to view the calendar and do all of the other Exchange type stuff that the users are used to.