netjammr.net - technorata http://netjammr.net/tech Thu, 10 Jul 2008 20:17:14 +0000 http://wordpress.org/?v=2.2 en Install and Configure Exchange Server 2003 http://netjammr.net/tech/2008/07/10/install-and-configure-exchange-server-2003/ http://netjammr.net/tech/2008/07/10/install-and-configure-exchange-server-2003/#comments Thu, 10 Jul 2008 14:16:38 +0000 admin http://netjammr.net/tech/2008/07/10/install-and-configure-exchange-server-2003/ winserv2003web1.png

This is the down and dirty for installing Exchange Server 2003 Standard Edition.

Windows Exchange Server 2003 Requirements

Content to follow….be patient.

Pre-Installation steps

There are a number of preparatory steps to carry out before installing Exchange server. These steps deal mostly with installing and configuring Windows Components required by Exchange server.

  1. From the Start menu, locate then click Control Panel. Next, click Add or Remove Programs.
  2. Click Add or Remove Windows Components to start the Windows Components Wizard.
  3. Click the Application Server component, and then click Details.
  4. Select the check box for ASP.NET, and then click OK.
  5. Scroll down to Internet Information Services (IIS) and click Details.
  6. Select the check boxes to select the following components:
    1. NNTP service
    2. SMTP service
    3. World Wide Web service
  7. Click OK to return to the Application Server components, and then click OK again to return to the main Windows Components Wizard page.
  8. Complete the wizard to install the components

ASP is a component of IIS, and is installed by default when you install the WWW service. However, you must enable ASP in the IIS services console though it is already installed. To do this, perform the following steps:

  1. Locate and click Administrative Tools and start the IIS Manager console.
  2. Expand the local computer, and then select Web Service Extensions.
  3. Select Active Server Pages, and then click Allow.

Domain and Network Diagnostics

Run dcdiag and netdiag after install Windows Supports Tools. These are command line tools

That is the last preparatory step, now we’ll go on to the actual Exchange installation.

Installing Exchange Server 2003

Forest Prep

The first step in installing Exchange Server involves updating the schema and configuration partitions in Active Directory by using Forest Prep. In simpler terms, Forest prep adds Exchange attributes to the Active Directory schema. Prior to running Forest prep, you will not find Exchange related tabs on AD user objects. After Forest prep, a user object will have the added Exchange related tabs;

  1. Email Address.
  2. Exchange Features.
  3. Exchange Advanced.
  4. Exchange General.
    5.

Forest prep needs to be run only once and in the root of the forest. It should be noted that Forest prep can take considerable time to execute, depending on the size of the organization. In a VM domain of 2 users, Forest prep took in excess of 10 minutes to complete. Your mileage may vary.

Insert the Exchange Server 2003 install CD and from the Run command type;

d:\setup\i386\setup.exe /forestprep

At this point the wizard will open the component selection portion of Setup. The sections should already be filled in. Click Next and you will be prompted for the Exchange Install Account…this account will be granted the Exchange Full Administrator role and will be given the authority to delegate other Exchange administrator roles. Click Next. Forest prep will now begin.

Domain Prep

The process for running domain prep is the same as for forest prep. At the Run command type:

d:\setup\i386\setup.exe /domainprep

The wizard will open the component selection portion of Setup. There is no need to change any value, Domain prep should be the listed option. Simply click Next.

]]> http://netjammr.net/tech/2008/07/10/install-and-configure-exchange-server-2003/feed/ Ubuntu Kernel update borks VMware http://netjammr.net/tech/2008/06/26/ubuntu-kernel-update-borks-vmware/ http://netjammr.net/tech/2008/06/26/ubuntu-kernel-update-borks-vmware/#comments Thu, 26 Jun 2008 13:57:12 +0000 admin http://netjammr.net/tech/2008/06/26/ubuntu-kernel-update-borks-vmware/ One of my favorite pieces of software is VMWare. I hate clutter, and VMWare allows me to run 2 (and more) OS’s on one system. At work, my host system runs Dapper Drake 6.06 LTS with Windows XP SP2 in a VM for Outlook and a few other Windows only programs. At home, my host system is Feisty 7.04 with a test domain complete with a Domain Controller, Exchange Server and an XP SP2 client to practice for MSCE’s in VMWare. I’ve just recently added a MOSS server to test prior to implementing at work. I interact with VMWare daily. It is the one piece of software that I would truly be lost w/out. In a word - indispensable.

That being said, every so often an Ubuntu update will render VMWare unusable. The update in question is a kernel update. After applying the update, and trying to open VMWare, nothing happens. No error, no fireworks - just blank.

To fix this, open a terminal and type:

sudo vmware-config.pl
VMware will begin the reconfiguration process that looks much the same as the initial install script. However, it will hang at the following line:
What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include]
If you hit enter, the following error line will be returned:
The path "/usr/src/linux/include" is not an existing directory.

Solution

Unfortunately, the kernel update won’t update the header files. Checking the path, /usr/src/linux/include/ will reveal your previous header files but the most recent is not present. A little tip: to check what kernel you are running simple type uname -r in a terminal. Anyway, a manual update is necessary to download the most up-to-date header files. So in a terminal, type:

sudo apt-get install build-essential linux-headers-`uname -r`
Now simply go back to the vmware configure script, vmware-config.pl and complete the header reconfiguration. This time around, VMWare automatically locates the C header files as seen in the highlighted text below:
What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.15-52-386/build/include]
Just click the Enter key to continue the update.

Note: Remember, to click Enter or type yes when coming to this line:

Would you like to skip networking setup and keep your old settings as they are? (yes/no) [yes]
to keep the old network settings. Otherwise, you’ll have to re-network everything!

So, after a kernel update, this 5 minute fix will have VMWare running good as new.

]]> http://netjammr.net/tech/2008/06/26/ubuntu-kernel-update-borks-vmware/feed/ Install and Configure Windows Server Update Services 3.0 - Part 2 http://netjammr.net/tech/2008/02/19/install-and-configure-windows-server-update-services-30-part-2/ http://netjammr.net/tech/2008/02/19/install-and-configure-windows-server-update-services-30-part-2/#comments Tue, 19 Feb 2008 16:20:58 +0000 admin http://netjammr.net/tech/2008/02/19/install-and-configure-windows-server-update-services-30-part-2/ microsoft.gif

This is the second part of a two-part article on Installing and Configuring WSUS 3.0. The first part can be found here

Configuring WSUS 3.0

The WSUS 3.0 configuration wizard will be run immediately after installation or at a later time. If you want to change the configuration later, you run WSUS Server Configuration Wizard from the Options page of the WSUS 3.0 Admin console.

Choose the upstream server

  1. Click Next in the Before you begin section. We don’t have to worry about this since we have no proxy server or corporate firewalls to configure.
  2. In the next screen I opted out of the Microsoft Improvement Program.
  3. On the Choose Upstream Server page, select the source from which this server will get its updates (Microsoft Updates or another WSUS server). I chose Synchronize from Microsoft Updates.
  4. This installation assumes no proxy server configuration and a single upstream server so you are finished with this step, just click Next

Connect to the upstream server

  1. Click the Start Connecting button, which will save and upload your settings and then download information about available updates, products and classifications.
  2. If there are problems with the connection, use the Stop Connecting button.
  3. After a successful connection, click Next then go on to the Choose Languages page and click Next.
  4. In the Choose Products and Chose Classifications sections I chose items most pertinent to my clients environments
  5. In the Configure Sync Schedule page I chose to synchronize on a schedule - around 2am for my WSUS server. Click Next and you’ll see that although you’ve scheduled a scan later, the server will do an immediate initial synchronization with the Microsoft Update site. Remember, the initial sync operation will take some time. Click Next and then Finish.

Creating Computer Groups

While your WSUS server is synchronizing, you can go ahead and plan out what computer groups you’d like to set up in the WSUS Admin console. This will depend on your environment. Maybe you’d like to group your update clients in a manner similar to your AD OU’s or maybe by floors or physical locations? It might also be a good idea to have a test group to vet out any new updates. If the test group okay’s the updates, they are clear to push to the remainder of your organization.

Creating groups is very easy. Open the WSUS Admin console, locate the Computers node, right-click and select Add Computer Group. Name your Computer group and click OK.

Configure Client Updates

There are two methods of ensuring Automatic Update clients are receiving updates from your WSUS server. The first is by using Group Policy and the second is by configuring client registry’s or Local Group Policy Object. Since I’m using AD, I will use the former Group Policy method.

First of all, you must upgrade all XP clients to SP2 if not already done so as SP has the latest compatible version of Automatic Updates that syncs with WSUS. Vista clients require no upgrade. As for Windows 2000 or 98, you’re on your own.

After ensuring all clients are either Vista or XP SP2, I’m going to create a GPO to configure client updating

Microsoft recommends that you not use the Default Domain Policy to configure client updates so I went ahead and created a new one (WSUS Domain Policy) and added it to my Admin MMC console. I’m controlling my WSUS Policy from my DC but you can use any system you want really. However, you need to ensure that the WSUS Administrative Template is loaded. To do that simply click the Administrative node, either one will do, then from the main menu select Action, click Add/Remove Templates, click Add, and select wuau.adm. In the Add/Remove Templates dialog box, click Close. You might already have the Administrative template, if so, that’s one less step for you.

To configure Automatic client updates we’ll need to edit the WSUS Domain Policy I created earlier. Simply follow these steps:

Configure Automatic Updates

  1. In the Group Policy Object Editor, expand Computer Configuration, expand Administrative Templates, expand Windows Components and then click Windows Update.
  2. In the details pane, click Configure Automatic Updates
  3. Click Enabled. You will also see several Update options. I won’t go into the details of each one. They are self-explanatory. I chose to Auto download and schedule the install so as to keep things as automated as possible.

Next, we’ll need to specify the location where the clients attempt to download updates, specifically our WSUS 3.0 server.

Specify intranet Microsoft Update service location

  1. In the Group Policy Object Editor, expand Computer Configuration, expand Administrative Templates, expand Windows Components and then click Windows Update.
  2. In the details pane, click Specify Intranet Microsoft update service location
  3. Click Enabled and type the HTTP(S) URL of the same WSUS server in the Set the intranet update service for detecting updates box and in the Set the intranet statistics server box. For example, type http(s)://servername in both boxes where servername is the name of the server. If the port is not 80 for HTTP or 443 for HTTPS, you should add the port number: https://servername:portnumber

Automatic Update detection frequency

The specifics of this policy deal with how often clients check for new updates. It’s in the same node as the two above examples. I’ve set mine to check every 12 hours.

Command-line Options

Usage of the command line can come in handy sometimes. To immediately enforce any Group Policy updates, simply type:

gpupdate /force.

To force a client to detect its’ assigned WSUS Intranet server, type:

wuauclt.exe /detectnow.

In addition, if you are using client-side targeting to assign group computer membership type the following to initiate detection and update group membership:

wuauclt.exe /resetauthorization /detectnow

Conclusion

I’ve touched upon one simple implementation of WSUS 3.0 - there are many other, more complex scenarios however. This is definitely a product that Windows IT Administrators can put to good use, with minimal effort.

]]> http://netjammr.net/tech/2008/02/19/install-and-configure-windows-server-update-services-30-part-2/feed/ Install and Configure Windows Server Update Services 3.0 - Part 1 http://netjammr.net/tech/2008/02/18/installing-windows-server-update-services-30/ http://netjammr.net/tech/2008/02/18/installing-windows-server-update-services-30/#comments Mon, 18 Feb 2008 18:13:32 +0000 admin http://netjammr.net/tech/2008/02/18/installing-windows-server-update-services-30/ microsoft.gif

Microsoft receives quite a bit of flak for their monopolistic tendencies and uninspiring software but to their credit, from time to time they release some useful products. One piece of software that is quite useful is Windows Server Updates Services or WSUS. In this article I’ll cover some requirements and go through an install using VMware Server Console.

This is part one of a two part article.


WSUS 3.0 SP1 Requirements on Windows Server 2003 SP1

  1. Microsoft Internet Information Services (IIS) 6.0.
  2. Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP 5.1 Windows Server 2003.
  3. Microsoft .NET Framework Version 2.0 Redistributable Package (x86).
  4. Microsoft Report Viewer Redistributable 2005.
  5. Microsoft Management Console 3.0 for Windows Server 2003.
  6. System and WSUS install partition must be NTFS.
  7. Minimum 1GB of free space on the system partition.
  8. Minimum 20GB of free space in recommended for the volume where WSUS stores updates - 30GB is recommended. For purposes of demonstration, I will use 8GB.
  9. A minimum of 2GB of free space where WSUS setup installs Windows Internal Database.

Please check the WSUS 3.0 SP1 page for Windows Server 2008 requirements, there are some differences. I would also suggest browsing through Deploying Microsoft Windows Server Update Services and Step-by-Step Guide to Getting Started with Microsoft Windows Server Update Services 3.0 for in depth information regarding the following installation.

A few other points to note, you cannot upgrade from WSUS 2.0 to WSUS 3.0. You must uninstall the previous version before installing WSUS 3.0.

Prepatory steps to installation

Before commencing with installation, two elements in your network need to be considered, if you have them. The first is your Proxy Server, the second is your firewall.

Proxy Server considerations

  1. What protocols are supported by your proxy server? WSUS uses HTTP and SSL so your proxy server will need to support both.
  2. The authentication method used by the proxy server (basic vs Windows authentication).

Firewall considerations

  1. Your firewall must allow traffic thru port 80 (HTTP) and 443 (SSL) - this is not configurable.
  2. If those ports are opened but restricted to certain sites, please see Deploying Microsoft Windows Server Update Services for an exhaustive list of required domains.
  3. Corporate firewall configuration is separate from Windows firewall on the WSUS server.
  4. Any downstream servers can be configured to use ports other than 80 and 443, however this does not apply to the upstream server communicating directly with the Microsoft Update site.

Required Software

So, first I’m going to install and configure IIS 6.0

  1. Click Start, select Control Panel and then click Add or Remove Programs.
  2. Click Add/Remove Windows Components
  3. In the Components list select Application Server. Click Details and make sure that ASP.NET is selected
  4. Click OK , click Next, and then follow the instructions on the screen.

After IIS is installed, download and install the following:

  1. Note: If the server you are installing WSUS 3.0 on hasn’t been updated you may need to download and install Windows Installer 3.0 Redistributable first. Also, I went ahead and installed Server 2003 SP2 because MMC 3.0 wouldn’t install without SP1 or higher.
  2. Microsoft .NET Framework Version 2.0 Redistributable Package (x86).
  3. Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP 5.1 Windows Server 2003.
  4. Microsoft Report Viewer Redistributable 2005.
  5. Microsoft Management Console 3.0 for Windows Server 2003.

Installing WSUS 3.0

Now that all the prerequisites are out of the way we can go ahead and install WSUS 3.0.

  1. Double click the installer file.
  2. On the Welcome page, click Next.
  3. On the Installation Mode Selection page, select the Full Server installation including Administration Console check box, and then click Next.
  4. Accept the license agreement and then click Next
  5. On the Select Update Source page, you can specify where the updates will be stored. I added an additional virtual 8Gb hard drive to store updates so that the location read: E:\WSUS\. Make sure that the check box Store updates locally is checked otherwise clients will update directly from the Microsoft Update site.
  6. Click Next
  7. On the Database Options page, select the software used to manage the WSUS database. I chose the default Microsoft SQL Server 2005 Embedded Edition and then clicked Next. The location should be the same as the step above E:\WSUS\
  8. On the Web Site Selection page, you specify the Web site that WSUS will use to point client computers to WSUS. Unless you already have a website using port 80 on the server you are installing WSUS on, go with the recommended selection. Choose the second option to install WSUS using the alternate port 8530. Click Next
  9. On the Ready to Install Windows Server Update Services page, review your choices and then click Next
  10. The final page of the install wizard will tell you whether or not WSUS 3.0 was completed successfully. After you click Finish the configuration wizard will be launched

Now that we’re finished with the installation, we can take a break and come back later or go on to the next step, Configuring WSUS 3.0

]]> http://netjammr.net/tech/2008/02/18/installing-windows-server-update-services-30/feed/ Setup a backup server with FreeNAS http://netjammr.net/tech/2008/02/03/setup-a-backup-server-with-freenas/ http://netjammr.net/tech/2008/02/03/setup-a-backup-server-with-freenas/#comments Sun, 03 Feb 2008 21:30:13 +0000 admin http://netjammr.net/tech/2008/02/03/setup-a-backup-server-with-freenas/ freenas.jpg

A few years ago my data added up to a few Gig and backups were a simple matter of adding another mirrored hard drive to my one trusty Dell 700XPS. However, as my home network has expanded with music, image and video data and several computers and laptops, I found the need for a dedicated backup box essential.

My requirements were simple. It needed to be free, easy to configure, scaleable, somewhat well documented and have miserly system requirements. There are many open source solutions out there but I decided to implement FreeNAS.


The box I used for this had the following specs:

  • System: Dell PowerEdge 400SC
  • Proc: Intel Pentium 4 Northwood 2.8Ghz
  • Memory: 2Gb - 4 x 512Mb
  • Video: Rage XL
  • OS drive: 40Gb Seagate Barracuda 7200.7 UltraATA
  • Data drive: 200Gb Western Digital WD2000JB
  • Optical drive: LG Superdrive DVD/CD-RW

Just a quick note on the above system specs. While a 2.8Ghz Northwood and 2Gig of RAM is by no means bleeding edge performance, I also realize it’s not exactly miserly. However, it’s the only spare system I had and I’m not going out to buy a weak Celeron system with 256Megs of RAM to demonstrate how efficiently FreeNAS uses system resources. With that said, let’s go on to the installation.

INSTALLATION

  1. Download the lastest stable image from the FreeNAS site and burn image to CD
  2. Boot up your system with FreeNAS LiveCD (not the embedded *.img)
  3. Hit Enter when the FreeNAS splashpage appears.
  4. Select 9 to install to your harddrive
  5. Select 3 to install full release
  6. FreeNAS setup will list the detected CDROM. Mine was acd0
  7. The next prompt was to enter the name of the CD-ROM drive, I entered acd0 that the install routine detected.
  8. A list of detected drives will be listed and a prompt Enter the name of the hard drive. This drive will be the FreeNAS installation drive not the data drive.
  9. My listed drives were:
    ad0: 38146MB
    ad1: 190783MB
  10. I typed the following for my OS drive - ad0
  11. At the next prompt, type in the size of your OS partition. I’m utilizing the entire disk so I typed the following: 38146
  12. The OS will install and then you are free to reboot the system
  13. The next step is to assign the LAN interfaces.
  14. After entering back into the setup menu, select 1 - Assign Interfaces.
  15. My installation automatically detected the interface - in my case em0 and that is what I typed when prompted to enter my LAN interface.
  16. I don’t want to configure additional (Optional) interfaces, so in the next screen I just hit the Enter key and in the next screen applied any changes by typing y
  17. In the main menu I selected 2 - Set LAN IP Address
  18. I typed n when asked if I wanted to use DHCP for IPv4 and then entered my preferred static IP address
  19. My LAN subnet bit count was 24 and my IPv4 gateway was my router at 192.168.1.1
  20. I also added my DNS information, external Comcast but I’m not sure if I should have just pointed it to my internal Linksys router - not sure if it does forwarding automagically.
  21. I configured IPv6 to configure automatically and then sent a test ping to my router. Looks good so far.
  22. So you should get a message about the assigned address and that you can access the WebGUI there.
  23. I logged on to mine at 192.168.1.30 - w/username: admin and password freenas.
  24. Once logged in, I went ahead and modified some of my network settings. I changed to reflect my network name suffix and also added a DNS server address. I also went ahead and changed the WebGUI password.
  25. Go to Disks -> Management and click on the + sign.
  26. On the next page, select the disk you want to use as your Backup directory. In my case, ad1 as noted earlier in these instructions
  27. In the Preformated FS drop down, we will leave the value as Unformated, click Add and in the next windowApply
  28. Next we want to format the disks. I selected ad1 and UFS with soft updates
  29. Now to mount the disk we use Disks -> Mount Point, click the + sign and select the disk to mount. I used the following values:
    Partition: EFI GPT
    File System: UFS
  30. Click Save and Apply
  31. Now we need to start a few daemons, specifically enabling CIFS/Samba
  32. Click the Services -> CFS/SMB link and check the Enable box.
  33. Leave all the default values and click the Save button for now. We’ll go back and change things as needed.
  34. Apparently as of version 0.685b we need to assign shares. So click the Shares tab and enter the appropriate information. I used the browse button to select the right syntax for the file path and also unchecked the Hosts deny option.
  35. At this point, in a Windows system I am able to type \\192.168.1.30 in the Run command and access the share. On Gutsy I can open Nautilus, click Go -> Location and type in the ip address and access the share as well.
  36. Now that we’ve tested CFS/SMB access, we want to go ahead and allow our *nix systems native access with NFS. Locate and click Services -> NFS
  37. Check the enable check box. Enter the correct subnet that will have access, including the subnet mask which in my case was 192.168.1.0/24. Click Save and Restart and make sure that enable is checked. Let’s test now.
  38. Well, I see it but it’s not listed in my normal network because I haven’t edited those network settings. It shows up in Workgroup and the only place i can see to change that is in CFS/SMB.
  39. Change the workgroup name to whatever you network name is - in my case it is homenet.local Click Save and restart
  40. Checked it again and there it is. Easy.
]]> http://netjammr.net/tech/2008/02/03/setup-a-backup-server-with-freenas/feed/ RIAA website hacked http://netjammr.net/tech/2008/01/21/riaa-website-hacked/ http://netjammr.net/tech/2008/01/21/riaa-website-hacked/#comments Mon, 21 Jan 2008 17:32:40 +0000 admin http://netjammr.net/tech/2008/01/21/riaa-website-hacked/ glider.jpeg

Ah, this is sweet justice. What kind of crappy web team do they have that leaves such a high profile site open to SQL Injection attack? n00bz.

]]> http://netjammr.net/tech/2008/01/21/riaa-website-hacked/feed/ MacBook with Ubuntu Feisty Fawn 7.04 http://netjammr.net/tech/2007/11/26/macbook-with-ubuntu-feisty-fawn-704/ http://netjammr.net/tech/2007/11/26/macbook-with-ubuntu-feisty-fawn-704/#comments Tue, 27 Nov 2007 02:52:16 +0000 admin http://netjammr.net/tech/2007/11/26/macbook-with-ubuntu-feisty-fawn-704/ ubuntulogo.png

The last few years I have really become a fan of the Linux distribution, Ubuntu. I’ve tried other distro’s and they each have their good points but what I liked about Ubuntu was the large community and expansive support. Not only that, but Ubuntu is a snap to get up and running. Yes, I’ve set up a Debian and a Slackware box but at this point I’m more impressed by a distro that I can start using immediately with minimum fuss.

That being said, I am also a fan of the latest Apple MacBook. It’s small, powerful and now that it’s powered by Intel processors, I don’t have to settle for a PPC version of Linux. So below is a down and dirty on the steps I took to set up my MacBook with Ubuntu 7.04. Your mileage may vary….

INSTALLATION

  1. Insert CD: Follow all default instructions, (US Keyboard, EST time zone, Partition entire disc, etc…)
  2. After installation is complete reboot and enter configuration phase

HOSTNAME

  1. Open System > Administration > Network and change hostname to nixbook.somenet.local. In addition, add correct DNS settings.
  2. In Hosts tab edit IP address with correct Alias information (192.168.1.x = nixbook.somenet.local, 127.0.1.1 = nixbook.somenet.local, 127.0.0.1 = localhost, nixbook.somenet.local)

REPOSITORIES

  1. Go to http://ubuntuguide.org/wiki/Ubuntu:Feisty#How_to_add_extra_repositories to edit correct repositories.
  2. Run sudo apt-get update to acquire all updates

DISPLAY RESOLUTION

  1. sudo apt-get install 915resolution
  2. Ctrl + Alt + Del to restart GDM and then edit display settings.

COMPILE TOOLS

  1. sudo apt-get install build-essential or sudo aptitude install build-essential

TOUCHPAD

  1. see http://help.ubuntu.com/community/macbook
  2. For touchpad delay, this site has some good info….

FONT SMOOTHING

  1. add the following lines to /etc/apt/sources.list
    deb http://wwww.telemail.fi/mlind/ubuntu feisty fonts
    deb-src http://www.telemail.fl/mlind/ubuntu feisty fonts
  2. sudo aptitude install libfreetype6 libcairo2 libxft2

WINDOWS FONTS

  1. sudo apt-get install msttcorefonts

SPEED UP GNOME

  1. Open your text editor of choice and copy and paste in the following text:
    gtk-menu-popup-delay = 0"| tee -a .gtkrc-2.0
  3. Save the file into your home directory with the name .gtkrc-2.0 (don’t forget the period before the filename), and restart your session (CTRL+ALT+BACKSPACE). You’ll notice a nice speed boost when browsing within a category in your menu.
  4. 1. gtk-menu-popup-delay = "0" | tee -a gtkrc - 2.0
    2. Save into home directory

WIRELESS

  1. Go to NDISWrapper home page http://ndiswrapper.sourceforge.net. Find the installation page and follow instructions
  2. Make sure before compiling that you have sudo apt-get install build-essential to compile programs
  3. Download latest NDISWRAPPER version; 1.4.9 as of Nov 2007.
  4. After downloading to your desktop, go to the source-directory and run make distclean and make. As root, run make install. This should compile and install both the kernel module and the userspace utilities.
  5. Go to the “List” page in the NDISWRAPPER web page to find your version of wireless card. First, identify the type of card you have with lspci.
  6. To identify the driver that you need from List, first identify the card you have with lspci and note the first column such as 0000:00:0c.0 and then find out the PCI ID of the card by running lspci -n and locating the entry corresponding to the first column of lspci output. The PCI ID is third column or fourth in some distributions and of the form 104c:8400. Now you need to get the Windows driver for this chipset.
    In the List, find out an entry for the same PCI ID, and download the driver corresponding to it. Unpack the Windows driver with unzip/cabextract/unshield tools, and find the INF file (.INF or .inf extension) and the SYS file (.SYS or .sys extension). If there are multiple INF/SYS files, you may look in the List if there are any hints about which of them should be used. Make sure the INF file, SYS file and any BIN files (For example, TI drivers use BIN firmware) files are all in one directory.
  7. In the list I looked under “A” for the Atheros card that is standard on the Mac Core Duo 2’s . The executable on my desktop was from the Lenovo site and was 7iwc28ww.exe. The command to cabextract was cabextract filename, easy as can be!!
  8. Now use ndiswrapper to install. ndiswrapper -i NET5416.INF
  9. This copies all necessary files to /etc/ndiswrapper and creates the config files for your card. After installing you can run ndiswrapper -l to see the status of your installed drivers. You should see something like:
    net5416 : driver installed
    device (168C:0024) present
  10. Then you have to load the interface with modprobe, type this before hand to ensure there are no errors. depmod -a then modprobe ndiswrapper. The drivers should be loaded, now just ensure that your wireless interface is configured correctly by going to System > Administration > Network and ensure that your wireless interface is active.

WICD

  1. These steps are optional…I got WICD working intermittently - maybe it’s more stable since this post?
  2. Go to WICD sourceforge download package.
  3. sudo apt-get remove network-manager even if a fresh install.
  4. …or simply use Synaptic Package manager > search for WICD and install. It will remove other possible conflicting pages but continue with installation.
  5. To install it in the task tray open System > Preferences > Sessions, click new > in the name field type WCID and in command type /opt/wicd/tray.py

MULTIMEDIA

  1. changed /etc/apt/sources.list and changed all entries "http://us.archive...." by omitting the “us” nation portion.
  2. then added "deb http://packages.medibuntu.org/" to my list or use this one "http://ubuntuguide.org/wiki/Ubuntu:Feisty#How_to_add_extra_repositories"
  3. then do sudo apt-get install w32codecs
  4. then do sudo apt-get update and sudo apt-get install libdvdcss2
  5. Afterwards you can install mplayer and vlc.
  6. Ensure that you go into each players preferences section and edit the codecs being used. VLC was changed to the X11 codec and I think I set mplayer to OpenGL

VMWARE SERVER

  1. http://www.howtoforge.com/ubuntu_feisty_fawn_vmware_server_howto
  2. to find kernel version: sudo uname -r
  3. change old command sudo vmware-install.pl to sudo ./vmware-install.pl
  4. also run sudo apt-get install libx11-6 libxtst6 libice-dev libsm-dev libxt6
  5. continue with installation choosing defaults

VERSION CHECK

  1. in terminal lsb_release -a

FAN

  1. sudo sh -c "echo 6000 > /sys/devices/platform/applesmc/fan0_minimum_speed more than likely set for less, say 4500 (11.26.07)
  2. You must ensure you have the correct privileges assigned

JAVA

  1. Firefox plugin: sudo apt-get install sun-java6-plugin
  2. JAVA JDK: sudo apt-get install sun-java6-jdk
  3. Check version: java -version

That was easy!

]]> http://netjammr.net/tech/2007/11/26/macbook-with-ubuntu-feisty-fawn-704/feed/ Installing Windows Server 2003 Standard Edition http://netjammr.net/tech/2007/11/19/installing-windows-server-2003-standard-edition/ http://netjammr.net/tech/2007/11/19/installing-windows-server-2003-standard-edition/#comments Tue, 20 Nov 2007 03:15:08 +0000 admin http://netjammr.net/tech/2008/01/19/installing-windows-server-2003-standard-edition/ winserv2003web1.png

Possibly I’m bored or I am actually being responsible and documenting a successful Server 2k3 install. I attempted something similar last year using a wiki when I was studying for an MSCE exam (I passed thanks much). Since then I’ve been busy with web development projects and haven’t had much reason to mess with Windows server’s aside from basic administration tasks. However, I’m getting the itch to get back on track and finish my MSCE and where better to start than by documenting a Windows Server 2003 installation.

Note: This is all being done in VMWare Server on a Linux host OS - Ubuntu Gutsy to be specific.

Windows Server 2003 Requirements

Let’s do away with all the obvious stuff.

  1. Computer and processor: 133-MHz processor required; 550-MHz or faster processor recommended; support for up to four processors on one server.
  2. Memory: 128 MB of RAM required; 256 MB or more recommended; 4 GB maximum.
  3. Hard disk: 1.2 GB for network install; 2.9 GB for CD install.
  4. Drive: CD-ROM or DVD-ROM drive.
  5. Display: VGA or hardware that supports console redirection required; Super VGA supporting 800 x 600 or higher-resolution monitor recommended.

On with the installation…

So before I continue, I’ll just add the obvious fact that we’ll need the space formatted for NTFS. So next…

  1. Insert the CD, boot up the system, install in the desired partition using NTFS (NTFS Quick is fine too) and let the setup finish.
  2. When prompted for licensing scheme, I selected the option that clients would have licenses. It’s a guess and what made me decide to do this write up in the first place.
  3. After setup is complete, login. There is no domain to log into yet, we’ll create the domain shortly.
  4. After logging in, a large window will appear labeled ManageYour Server. Locate and click the add or remove a role link. This is where we’ll begin to create our domain controller.
  5. On the Configuration Options page, since this is our first server in the domain, we will select Typical configuration for a first server.
  6. In the Active Directory Domain Name page we will give our domain a name. Mine is TestNet.local. I used the default .local extension but Microsoft allows others as well.
  7. On the NetBIOS Name page I used the default provided given my AD Domain name; TESTNET.
  8. You should be presented with a summary of configuration options at this point. Mine was:
    Install DHCP server (if required)
    Install Active Directory and DNS server (sets up this server as a domain controller)
    Create the following full domain name: TestNet.local
  9. Click Next and the configuration will be applied and the system will restart.
  10. Log back in (you’ll see the domain name listed now) and a page presents you with all the configuration changes.
  11. Okay, now let’s do all our Windows updates. This will take some time. So fire up IE, start the updates and go grab some coffee or stimulant of choice.

That’s enough for now…I’ll cover finishing the install in Part 2

DNS Configuration

So now we’ll configure our DNS, specifically I want to check that reverse lookups are have been installed.

  1. Open DNS Management, then expand your server node
  2. Locate and right click the folder Reverse Lookup Zones selecting New Zone
  3. Click Next and in the next window select Primary Zone
  4. Click Next and select To all DNS servers in the Active Directory forest…
  5. Click Next and input your network number in the area labeled Network ID. So for a refresher, if your network range was 192.168.1.1 - 254 your Network ID would be 192.168.1. Click Next
  6. If prompted to configure Dynamic Updates, select Allow only secure… just to be safe. This will only allow AD clients to alter DNS records so remember if you’ll need to manually update entries for non-AD members.
  7. Click Finish

So that’s it, pretty easy. Something to note, you won’t see your DNS clients immediately creating their PTR or reverse lookup records, it can take some time. As long as you followed the instructions in Step 6 above, your AD clients will update dynamically. However, if you can’t wait, you can create the resource record by right clicking in the Reverse Zone node and selecting New Pointer (PTR).]]> http://netjammr.net/tech/2007/11/19/installing-windows-server-2003-standard-edition/feed/ Memory Leak! http://netjammr.net/tech/2007/10/12/memory-leak/ http://netjammr.net/tech/2007/10/12/memory-leak/#comments Fri, 12 Oct 2007 15:56:37 +0000 admin http://netjammr.net/tech/2007/10/12/memory-leak/ Working in IT, staff, clients and even friends seeking free advice seem to labour under the delusion that my brain is a computer. I guess technically it’s sort of an analog one but that’s a stretch at best. So when a non-techie asks me what the speed difference is between USB 1.0, 2.0 and Firewire and I suggest they Google it, I’m usually greeted with looks of amazement as if worms are shooting out of my nose. Little do they realize that Google is my backup brain. Holy crap, my Comcast went down the other week and it was like an instant frontal labotomy.

This article on Wired makes me feel less lonely, yet no less worried.

]]> http://netjammr.net/tech/2007/10/12/memory-leak/feed/ Holy Paranoia Batman! http://netjammr.net/tech/2007/08/14/holy-paranoia-batman/ http://netjammr.net/tech/2007/08/14/holy-paranoia-batman/#comments Tue, 14 Aug 2007 21:35:34 +0000 admin http://netjammr.net/tech/2007/08/14/holy-paranoia-batman/

I came upon this article after reading about John Young’s Cryptome.org on BoingBoing. My first reaction was that the author needed to take a deep breath, walk over to the bar, pour out a nice glass of single malt, (neat of course), sit down and relax.

By the end I was making a mental list of all the security holes I had that he mentioned! Yikes, I use Linux at home but I think that’s the only thing I have going for me.

]]> http://netjammr.net/tech/2007/08/14/holy-paranoia-batman/feed/