In other news, Microsoft has granted me access to System Center Service Manager. I am going to dig into that product to see how it compares. If it accomplishes 80% of what Infra accomplished, I may be sold.

Open terminal and create a link to the utility.

1

sudo ln -s /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport /usr/sbin/airport

Now that the utility is available, run airport -I for all of your wireless information.

1

sudo chmod u+s /usr/sbin/pppd

This will enable NetExtender to once again work its magic.

Boot Keyboard Shortcut

Hold down the ’6′ and ’4′ keys while you are booting. Conversly, you can boot into 32bit by holding down the ’3′ and the ’2′ keys.

NVRAM setting

Set a nvram setting to boot into 64bit.

nvram boot-args="arch=x86_64"

Apple Configuration File

Set to Apple configuration file to boot into 64bit by editing /Library/Preferences/SystemConfiguration/com.apple.Boot.plist

< ?xml version="1.0" encoding="UTF-8"?>
<  !DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
< plist version="1.0">
< dict>
	< key>Kernel< /key>
	< string>mach_kernel< /string>
	< key>Kernel Flags< /key>
	< string>arch=x86_64< /string>
< /dict>
< /plist>

Don’t bother trying to install the Windows 2003 Admin Tool Pack in Windows 7.  It will not work.

Microsoft has released the Remote Server Administration Tools for Windows 7.  Download and install this little jewel.  Once installed, hop into your “Control Panel”.  Click on “Programs” and then “Turn Windows features on or off”.  You will see a new section called “Remote Server Administration Tools”.  Mark which tools you need and then click Ok.  No reboot needed.

That was half the problem…  Now onto the Exchange tools.  Microsoft seems to not have much information about the Exchange tools for 2003.  I can’t blame them.  I would like to be running Exchange 2007 right now but it is not in the cards for another year.  By that time, probably jump right into Exchange 2010.  In the meantime, I found a download over at Will Dove’s website.  What he has done is take the official ESM for Vista build from Microsoft and removed the check for Vista in the install process.  This works like a charm.  I have not run into any issues using this on my system.

Next up for my admin tool build project, Citrix Tools and OCS.

Updates:

• 20090817 – Updated the link to the Remote Server Administration Tools

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

LDAPRootDN = "LDAP://OU=HCL Users,DC=hcl,DC=internal"
 
' Infra database DSN
InfraDSN = "Driver={SQL Server};Server=data01.hcl.internal;Database=infraEnterprise;Trusted_Connection=TRUE"
 
set objConnection = CreateObject("ADODB.Connection")
objConnection.ConnectionString = InfraDSN
objConnection.open
 
' Start the process
ProcessOU(LDAPRootDN)
 
function ProcessOU ( DN )
    set CNUsers = GetObject(DN)
    for each User in CNUsers
        select case User.class
            case "user"
                ' Migrate manager information if a manager is defined
                if ( User.manager <> "" ) then
                    MigrationCount = MigrationCount + 1
                    MigrateManager User.distinguishedName, User.manager
                else
                    ' No manager information on file
                end if
            case "organizationalUnit", "container"
                ' This is an OU, recurse into
                ProcessOU( User.ADsPath )
        end select
    next
end function
 
function MigrateManager ( StaffDN, ManagerDN )
    set Staff = GetObject("LDAP://" + StaffDN)
    set Manager = GetObject("LDAP://" + ManagerDN)
    strQuery = "exec sp_MigrateManager '" + Staff.GUID + "', '" + Manager.GUID + "'"
    set rs = objConnection.execute(strQuery)
end function

The following is the supporting TSQL for the sp_MigrateManager procedure.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

 
USE infraEnterprise
GO
 
IF EXISTS ( (SELECT NAME FROM sysobjects WHERE NAME = 'sp_MigrateManager' AND TYPE = 'P'))
BEGIN
    DROP PROCEDURE sp_MigrateManager
END
GO
 
CREATE PROCEDURE sp_MigrateManager 
    @StaffGUID NVARCHAR(300),
    @ManagerGUID NVARCHAR(300)
AS
BEGIN
 
    DECLARE @ManagerRef INT
 
    SELECT @ManagerRef = COALESCE(REF, 0) FROM AR_USER_ATTRIBUTES WHERE ldap_object_id = @ManagerGUID
 
    UPDATE AR_USER_ATTRIBUTES
    SET
        MANAGER_REF = @ManagerRef
    WHERE
        ldap_object_id = @StaffGUID
 
END
 
GO

• IBM Thinkpad
• Cingular Aircard 875 (note, this is really a Sierra card)
• Ubuntu Hardy Heron 8.04 (updated system as of 20080510)

The first step was to make sure the drivers were being loaded into the system correctly when the hardware was inserted. The simple way to do this is tail the message log.

sudo tail -f /var/log/messages

Upon inserting the card, I saw that the card was recognized and that the device was assigned some ttyUSB device nodes.

Upon inserting card…

May 10 10:00:49 spicy kernel: [ 688.462393] sierra 5-1:1.0: Sierra USB modem (3 port) converter detected
May 10 10:00:49 spicy kernel: [ 688.463909] usb 5-1: Sierra USB modem (3 port) converter now attached to ttyUSB0
May 10 10:00:49 spicy kernel: [ 688.464288] usb 5-1: Sierra USB modem (3 port) converter now attached to ttyUSB1
May 10 10:00:49 spicy kernel: [ 688.464599] usb 5-1: Sierra USB modem (3 port) converter now attached to ttyUSB2
May 10 10:00:49 spicy kernel: [ 688.464833] usbcore: registered new interface driver sierra
May 10 10:00:49 spicy kernel: [ 688.464839] /build/buildd/linux-2.6.24/drivers/usb/serial/sierra.c: USB Driver for Sierra Wireless USB modems: v.1.2.5b

Make sure that you see the lines similar to “usb 5-1: Sierra USB modem (3 port) converter now attached to ttyUSB0”. This tells you that you will be able to use device ttyUSB0 to make your connection.

Now, this is the point where I could have used some of the config files in the previous post but I wanted to focus on using the GUI configuration tools.

So, click on the Network Manager applet and select “Manual Configuration”. Once this appears on your screen, click the “Unlock” button and authenticate.

Select the “Point to Point” connection and then click on the “Properties” button.

On the general tab, enter the following information:

• Connection Type: Serial Modem
• Phone Number: *99***1#
• Username: WAP@CINGULARGPRS.COM
• Password: cingular1

On the modem tab, enter the following information:

• Modem port: /dev/ttyUSB0

On the options tab, select the following check boxes:

• Set modem as default route to Internet
• Use the Internet service providers nameservers

Click the “OK” button. Your ppp connection is now configured. You can close the “Network Settings” window. Now, logout of your gnome session. The key here is to restart the Network Manager applet so that it recognizes the new ppp connection.

Once you log back in, click on the Network Manager applet and select the “Dial Up Connections” option and then”Connect to ppp0 via Modem”. This will start you Cingular connection and you should be good to go.

Notes:

• You can monitor the connection progress by having a terminal widow open and executing the following command: ‘sudo tail -f /var/log/messages’
• Firefox may think that it is working offline when you first start the application. Click on ‘File’ → ‘Work Offline’ to make sure the option is not set. I was then able to browse with no problems.