setup

How To: Deploy MS Office to Mac

Posted by Rick on in Microsoft, Technology How To's 0 Comment

How To: Deploy MS Office to Mac

One of the biggest pains in deploying MS Office to OS X in a business or education environment is making sure that the serial number deploys too.

To do this, you need to also deploy the following files:

~/Library/Preferences/com.microsoft.autoupdate2.plist
~/Library/Preferences/com.microsoft.error_reporting.plist
~/Library/Preferences/com.microsoft.office.plist
~/Library/Preferences/com.microsoft.office.setupassistant.plist

Deploying these files will keep also keep the initial setup assistant from running upon first launch.

Deployment can be via any of your normal methods, Apple Remote Desktop being the “Apple Preferred Way,” of course.

How To: Fix Portable Ubuntu Remix in Windows

Posted by Rick on in Linux, Technology How To's 1 Comment

How To: Fix Portable Ubuntu Remix in Windows

The Portable Ubuntu Remix or pubuntu project allows Linux to run INSIDE Windows as a native win32 application. This is not the same as running Linux within a VMWare or Virtual Machine environment.

Recent versions have become much more stable, to the point that it’s now possible to even run Gnome (a typical Linux GUI Desktop). Screenshots can be found on Lifehacker.

Installing Pubuntu is actually pretty easy, just open the downloaded file, click on the application and follow the prompts.

The first thing to do after it’s installed is to change the default user and password. (pubuntu, 123456)

1. Open up a terminal
2. Type: adduser (Replace with the new user name from here down)
3. Enter the password 123456 if prompted for pubuntu’s password and then fill out the information it asks for
4. type: cd (Just to make sure you’re in the right directory)
5. type: cp ./* ..//
6. type: cp ./.* ..//
7. type: cd ../
8. type: chown *
9. type: chown .[^.]*
10. type: chgrp *
11. type: chgrp .[^.]*
12. type: sudo nano /etc/event.d/tty1
13. Find the line near the bottom that says: exec /sbin/mingetty –autologin pubuntu tty1
14. Replace pubuntu with the new name
15. press Ctrl+X, press Y, press ENTER
16. type: sudo nano /etc/init/tty1
17. Repeat steps 13-15
18. type: sudo visudo
19. Find the line that says: root ALL=(ALL) ALL
20. Underneath it, add the following line: ALL=(ALL) ALL
21. Repeat step 15
22. type: reboot

Every once in a while pubuntu’s fstab will get messed up. If it hangs when trying to launch, you need to do this:

1. Look for the pubuntu icon in your task bar, right click it, and click restore
2. In the terminal that pops up, press ESCAPE
3. type: mount -o remount,rw /
4. type: nano /etc/fstab
5. delete the “-e” at the beginning of a line, just after cofsX.
6. Press Ctrl+X, press Y, and press ENTER
7. type: nano /etc/init.d/postmount_pubuntu.sh
8. replace the first like (#! /bin/sh) with #! /bin/bash
9. Press Ctrl+X, press Y, and press ENTER (again)
10. type: reboot

Home Network Setup

Posted by Rick on in Hardware, Technology How To's, Unix, Windows 0 Comment

Home Network Setup

Originally Posted 11/20/2000. Ironically a lot of this is still useful.

 

Home Networking

 

 

            In the day and age of Multi-computer families, a frequent argument is, who gets to be online? The answer is simple, Modem Sharing or networking. Modem Sharing can be done one of several ways, using a regular Analog Modem (300 baud to 56.6K,) DSL or ADSL, ISDN and Cable modems. You could also be on a T-1 (or greater!) network connection, but then why are you reading this? J

           

 

Which one is right for me?

 

            Analog Modems

 

            Pros: Can be used anywhere a telephone is located.

            Cons: Limited to an upper bandwidth of 53K due to telephone regulations in the US. May be slightly higher in other countries. Modems also suffer greatly from phone line quality, crosstalk (where two or more wires touch each other in the wrong place therefore mixing the signal,) and any line noise at all. More then two low-bandwidth applications can easily make this almost worse then nothing. Ties up the phone line if you only have one.

 

            ISDN:

            Pros: Very fast, two 64K channels giving 128K total. Even one channel at 64K is cleaner and noticeably faster then 56k.

            Cons: Still only 128K, costs the same as DSL. In addition, totally against ISDN specs, some companies charge you for the 2nd line to automatically drop when an incoming or outgoing phone call is detected, so your phone is still tied up.

 

            ADSL/DSL:

 

            Pros: Very fast… minimum 265K maximum 7 megabits, makes this very, very fast. Phone lines do not get tied up at all. Can easily support multiple high-bandwidth applications (web browsers, games, large downloads, etc.) Can get a Static IP, which is very useful if you wish to run servers at home.

            Cons: Suffers slightly at the phone companies end due to misconfiguration. Such things as dropped carriers, being able to see other people’s computers (in Network Neighborhood.) and depending on the carrier, a slight slow down in bandwidth due to the phone company over selling it. Remember, at this point the phone company does not have to guarantee a certain amount of bandwidth… you simply have speeds up what ever your limit is.

 

            Cable:

 

            Pros: As above, very, very fast

            Cons: Suffers greatly from overselling of bandwidth. If other cable subscribers are all using it at the same time as you, they effect your speed. If you’re the only one in the area then it’s not a big deal. But frequently this slows down to speeds that are little better then a regular modem. Can’t get a Static IP number,  you’ll never be able to run a server, at least not very effectively.

 

Initial Setup

 

            First you need to get the network equipment. Your best bet for ease of configuration and portability is to get a couple of  mid-priced range network cards, (Kingston is a good bet) and a decent 100Base hub. (NetGear, Bay Networks, Intel.) You can buy cheaper cards such as SMC but they will effect your speed. If you can afford it, a switch is even better, giving you more bandwidth and speed. You’ll also want several lengths of networking cables too. J

            Second, your modem or router should be hooked up to one of the computers. In the case of some DSL routers, these can be directly hooked up to your hub. Other products have a DSL router and hub built in to the same unit. In my opinion this is unncessecary and could cause problems down the road. Remember to install the 2nd network card if it’s an external unit. (Cable and DSL only.)

            The third step is to setup the modem/router itself to connect to the network. This changes from different brands of Cable modems and routers. If you’re using a regular 56k modem, connect as you usually would.

            The last step is to make sure you know what your IP Address, DHCP Server (if needed,) DNS Server, Gateway and Netmask numbers are. You may or many not have all of these options. These have four numbers or “octets” like 255.255.255.0 or 192.168.1.0 Each of these numbers or octets can be anything between 0 to 255, with some exceptions.

            Your network should look something like this when you’re done:

            ISP -> Modem/Routers -> Computer -> Hub <-> Other computers

            One thing to point out, the computer plugged into the modem/router needs to be running an Operating system capable of doing routing. Windows 95 is not capable of doing this.  Windows 98 sorta does it, while Windows NT, ME, 2000, FreeBSD and Linux are all capable of doing so. Mac OS X being based off of FreeBSD can also do this. Windows 95 is capable of doing so with the help of a third party commercial piece of software. I personally run FreeBSD on  a 486 SX-25, recently upgraded to a Intel P-166 to do this. (BTW, it runs quicker and more efficiently then Windows NT or 2000 on a AMD –450 with 128 megs of RAM!)

 

Network Setup

 

            The Network hardware is pretty straightforward. One cable from each computer plugs into the hub or the switch. Each port should have a LED saying the port is active. Usually there is a 2nd LED that shows network traffic on that port of the hub.

            Start with the computer connected to the modem/router. The protocol that you wish to run is TCP/IP, make sure IPX/SPX and Netbui are both disabled unless you need them. Most games these days don’t care what protocol you’re running, but some of the older ones need IPX/SPX (Duke Nukem 3D, Warcraft, early Diablo releases, etc.) Having Netbui disabled helps keep people from hacking into your computer, there are hundreds of security holes in Windows with this protocol.

            After adding TCP/IP in the Network option under Control Panel Add in your network settings as provided by your ISP. Usually your ISP gives you instructions on how to do this, you’ll want to follow them. Test your dial-up and networking. The computer should run perfect.

            Now comes the tricky part, configuring the other computers. The easiest configuration is the dual network card and external modem/router option. The first NIC connected to the modem/router is configured exactly as it should be. The 2nd NIC’s TCP/IP Address should be one that is assigned by you. For ease you should pick something like 192.168.1.1 You can pick any number, but make sure the first three octets are all the same. Do not pick the same first three octets as the IP assigned to your 1st NIC… it will cause problems.

            Your Netmask is always 255.255.255.0 do not ever change this unless you know what you’re doing, your network will become unreachable. The Gateway address is the same as the IP address of the 1st network card. Keep in mind this is only for this card. Certain operating system will not accept this option either, but most Windows systems should.

            In addition some operating systems will need a flag set to make it a gateway or router machine. For instance, in FreeBSD and Mac OS X /etc/rc.conf needs the line “gateway=enable” This also invokes the NAT or “Name Address Translation” program. NT and 2000 should both give you a similar option.

            The 2nd (and all subsequent computers) will have an IP address of 192.168.1.x (where x is any number between 2 and 254, do not use 1 as it’s already used, 0 and 255 should also be reserved, Just in case.) Their Gateway address will be the IP of the 2nd network card in the first computer! DNS or Name Server address will be the same across all computers, unless you setup a nameserver, which for a small network I recommend against doing.

            For computer with a single network card, and a modem, the theory is the same. Use the gateway to be the IP number of the modem/router. Remember that IP numbers are assigned to Network interfaces, not to the computer. A computer can theoretically have an infinite amount of IP addresses, in reality it’s whatever number the operating system is capable of handling, at least 254 though, and more then most people will ever need.

            If you have a large amount of computers, say more then 5 or 6, you may want to look into assigning these IP numbers via DHCP, it’s initial setup is harder, but more robust with large networks, it also makes the client machines virtually Plug and Play.

 

            Security

           

            Now that your network is running, it’s time to turn your eye towards security. The best way is a firewall. Windows NT, 2000, FreeBSD and Linux can all do this. Linux has more security holes fixed then Windows NT or 2000, and FreeBSD even more. If you’re really serious about security and wish to really learn, OpenBSD is the best of all. FreeBSD offers the best choice of security and ease of setup.

            A Firewall is simply that, it keeps the bad stuff from coming in, and if you wish, keeps stuff from going out. It works by stopping or dropping traffic if it does not adhere to the rules that you define.

            The first step in building effective firewalls is to block everything. Then step by step you want to unblock stuff you want. Port 80 (http requests,) 21 and 22 (FTP) are good starts. Some programs will want other ports open, PCAnywhere needs 186 & 187 open. Remember, it’s easier to block stuff before it’s broken, then to block if after somebody has hacked into your computer.

 

            Conclusion

 

            These are really some very basic instructions. Unluckily due to the sheer amount of different configurations out there, I can’t give step by step instructions like I’d like too. If you have specific questions though, post to the Hardware and Software forums and somebody can help! J Even then you should have a working network configuration in no time at all!

How To: Synchronize Blackberry and Zimbra on OS X

Posted by Rick on in Apple, Technology How To's 0 Comment

How To: Synchronize Blackberry and Zimbra on OS X

At first looks there is no obvious way to synchronize RIM’s Blackberry devices with the Zimbra mail client. Blackberry already has a huge following in the business world while Zimbra is starting to become extremely popular as an Exchange replacement.

But, out of the box neither will talk to each other directly on OS X.

This can be resolved, but it’s actually a two step process so it will take a little bit of extra work to be sure that data does not get out of date.

Zimbra provides Apple iSync Connector which is currently bundled in the Network Edition Professional Server download, available in the trial version (signup required) or from the Admin Console in an already existing Zimbra install.

Install the iSync Connector with the directions here.

Once the connector is installed it’s a good idea to go ahead and do the initial synchronization. This will sync Calendar, Contacts, Notes, and the Address Book to the corresponding OS X Application. Email will of course not sync since the Blackberry can be setup as an email client and can receive the emails directly.

After the initial synchronization between Zimbra and the desktop, it’s now possible to sync the desktop with the Blackberry.

This is done with the PocketMac Application which is a free download for those who already have a Blackberry. It is not free for any other phone or PDA, although it does work with a wide variety of other systems.

Install PocketMac, plug in the Blackberry, hit the sync button on the dock and watch it all happen like magic.

Using this scenario it’s possible to get out of sync very easily though. I highly suggest getting in the habit of only making changes to one device ever, or doing this two step sync process immediately after adding or making changes.

How To: Budget Network Attached Raid 5 Fileserver, Part 3

Posted by Rick on in Hardware, Open Source, Technology How To's 0 Comment

The server is up and running, the drives are formatted and now serving just under 750gb of Raid5 goodness. Since I have a mixed network of machines, Windows and Mac I need to make it will work with each of those. So we’re going to setup SMB. I could also setup NFS as it’s slightly faster and would add compatibility to Linux machines but it’s not needed in this case. And SMB is actually a more common need since most people run Windows.

Again, counter intuitively I found it was best to setup users first before trying to setup the actual shares. There are two ways to do this. The easy way, or the secure way. If the NAS server is on a local home network, guest access may be the way to go. But I always suggest even in such cases to at least have basic security.Go to Access then Users and Groups. Type in the name of the first user and a password. Leave the User ID to default, it will increment automatically for every new user created. The next option, Primary Group has a drop down list of the standard Unix groups.      

Users and Groups   

The first user should be added to the admin group. Other groups can be staff and wheel. This will give the user maximum permissions to read and write files. Again for home use this is sufficient. Of course FreeNAS also has access to add LDAP and Active Directory authentication. Both of these are simple setups for any System Administrator.Since it’s first on the list, and there are more Windows users around, we’ll explore setting up SMB before NFS. Under Services go to CIFS/SMB. Click on the Shares Tab, then the Plus to add a new share. I simply called the name raid and put in a comment to note which raid it was. (In this case, raid because it’s the only one.) On the path option click on button with three dots. This brings up a filebrowser window, chose the raid directory that we’ve already setup and hit ok.  

File Browser  

 As can be seen below the it automatically puts in /mnt/raid which is what we setup back in Part 2.  

shares   

Before clicking the OK button notice two options for increased security. Host Deny and Host Allow. Adding in specific IP addresses to the allow box and ALL for deny will greatly increase security for connections. Keep in mind if the IP address of the computer changes, for instance DHCP on the DSL/Cable router is reset this could cause connection problems later on. At this point, the server is ready to test. Mac OS X 10.5(Leopard) actually sees these connections automatically, even if sharing across SMB (under file sharing) is turned off. Mac OS X 10.4 (Tiger) will need to connect to the drive via the Connect to Server option. Windows can now be connected just like any other server. Vista Directions are here, and Windows XP is here. 

FreeNAS is an incredibly powerful program. Even though it’s still only in Beta it seems like a very solid product and does RAID NAS very well. I’ve really enjoyed playing with it and want to give a big congratulations to the development team for a job well done.