Active Directory (50)
Articles and Books (96)
Final Cut Server (44)
Home Automation (15)
Mac OS X (933)
Mac OS X Server (764)
Mac Security (456)
Mass Deployment (371)
Microsoft Exchange Server (66)
Network Infrastructure (83)
Network Printing (4)
On the Road (58)
public speaking (63)
Social Networking (32)
Time Machine (7)
Wearable Technology (10)
Windows Server (124)
Windows XP (109)
- None Found
- Active Directory
- Articles and Books
- Final Cut Server
- Home Automation
- Mac OS X
- Mac OS X Server
- Mac Security
- Mass Deployment
- Microsoft Exchange Server
- Network Infrastructure
- Network Printing
- On the Road
- public speaking
- Social Networking
- Time Machine
- Wearable Technology
- Windows Server
- Windows XP
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
TagsActive Directory Apple Command line defaults DNS Final Cut Server Football Georgia georgia football Google howto Interview Tips ios iPad iPhone LDAP Linux Lion lion server MAC Mac OS X Mac OS X Server Mac Security Mass Deployment mavericks Mavericks Server mountain lion mountain lion server On the Road Open Directory os x OS X Server powershell profile manager script server 2.2 server 3 Snow Leopard UGA Video windows Windows Server Windows XP WordPress Xsan
Category Archives: Uncategorized
File Services are perhaps the most important aspect of any server because file servers are often the first server an organization purchases. There are a number of protocols built into OS X Mavericks Server dedicated to serving files, including AFP, SMB and WebDAV. These services, combined comprise the File Sharing service in OS X Mavericks Server (Server 3).
File servers have shares. In OS X Mavericks Server we refer to these as Share Points. By default:
- File Sharing has some built-in Share Points that not all environments will require.
- Each of these shares is also served by AFP and SMB, something else you might not want (many purely Mac environments might not even need SMB). Or if you have iOS devices, you may only require WebDAV sharing.
- Each share has permissions that Apple provides which will work for some but not all.
In short, the default configuration probably isn’t going to work for everyone. Therefore, before we do anything else, let’s edit the shares to make them secure. The first step is to create all of your users and groups (or at least the ones that will get permissions to the shares). This is done in Server app using the Users and Groups entries in the List Pane. Once users and groups are created, open the Server app and then click on the File Sharing service in the SERVICES list in the List Pane. Here, you will see a list of the shares on the server.
As mentioned, shares can be shared out using different protocols. Next, we’re going to disable SMB for Public. To do so, double-click on Public and then uncheck the SMB protocol checkbox for the share.
When you’ve disabled SMB, click on the Done button to save the changes to the server. Next, we’re going to create a new share for iPads to be able to put their work, above and beyond the WebDAV instance automatically used by the Wiki service. To create the share, first we’re going to create a directory for the share to live in on the computer, in this case in the /Shared Items/iPads directory. Then from the File Sharing pane in Server app, click on the plus sign (“+”).
At the screen for the iPads share, feel free to edit the name of the share (how it appears to users) as it by default uses the name of the directory for the name of the share. Then, it’s time to configure who has access to what on the share. Here, use the plus sign (“+”) in the Access section of the pane to add groups that should be able to have permission to access the share. Also, change the groups in the list that should have access by double-clicking on the name of the group and providing a new group name or clicking on the plus sign to add a user or group.
The permissions available in this screen for users that are added are Read & Write, Read Only/Read and Write. POSIX permissions (the bottom three entries) also have the option for No Access, but ACLs (the top entries comprise an Access Control List) don’t need such an option as if there is no ACE (Access Control Entry) for the object then No Access is assumed.
If more granular permissions are required then click on the name of the server in the Server app (the top item in the List Pane) and click on the Storage tab. Here, browse to the directory and click on Edit Permissions.
As can be seen, there are a number of other options that more granularly allow you to control permissions to files and directories in this view. If you make a share a home folder, you can use that share to store a home folder for a user account provided the server uses Open Directory. Once a share has been made an option for home folders it appears in both Workgroup Manager and the Server app as an available Home Folder location for users in that directory service.
Once you have created all the appropriate shares, deleted all the shares you no longer need and configured the appropriate permissions for the share, click on the ON button to start the File Sharing service.
To connect to a share, use the Connect to Server dialog, available by clicking Connect to Server in the Go menu. A change in Mavericks is that when you enter an address, the client connects over SMB. If you’d like to connect over AFP, enter afp:// in front of the address and then click Connect.
The File Sharing service can also be controlled from the command line. Mac OS X Server provides the sharing command. You can create, delete and augment information for share points using sharing. To create a share point for AFP you can use the following command:
sharing -a <path> -A <share name>
So let’s say you have a directory at /Shares/Public and you want to create a share point called PUBLIC. You can use the following command:
sharing -a /Shares/Public -A PUBLIC
Now, the -a here will create the share for AFP but what if you want to create a share for other protocols? Well, -F does FTP and -S does SMB. Once created you can disable the share using the following command:
sharing -r PUBLIC
To then get a listing of shares you can use the following command:
You can also use the serveradmin command to manage file shares as well as the sharing service. To see settings for file shares, use the serveradmin command along with the settings option and then define the sharing service:
sudo serveradmin settings sharing
Sharing settings include the following:
sharing:sharePointList:_array_id:/Users/admin/Public:smbName = "administrator's Public Folder"
sharing:sharePointList:_array_id:/Users/admin/Public:nfsExportRecord = _empty_array
sharing:sharePointList:_array_id:/Users/admin/Public:afpIsGuestAccessEnabled = yes
sharing:sharePointList:_array_id:/Users/admin/Public:isIndexingEnabled = no
sharing:sharePointList:_array_id:/Users/admin/Public:dsAttrTypeNative\:sharepoint_group_id = "35DF29D6-D5F3-4F16-8F20-B50BCDFD8743"
sharing:sharePointList:_array_id:/Users/admin/Public:mountedOnPath = "/"
sharing:sharePointList:_array_id:/Users/admin/Public:dsAttrTypeNative\:sharepoint_account_uuid = "51BC33DC-1362-489E-8989-93286B77BD4C"
sharing:sharePointList:_array_id:/Users/admin/Public:path = "/Users/admin/Public"
sharing:sharePointList:_array_id:/Users/admin/Public:smbIsShared = yes
sharing:sharePointList:_array_id:/Users/admin/Public:smbIsGuestAccessEnabled = yes
sharing:sharePointList:_array_id:/Users/admin/Public:afpName = "administrator's Public Folder"
sharing:sharePointList:_array_id:/Users/admin/Public:dsAttrTypeStandard\:GeneratedUID = "4646E019-352D-40D5-B62C-8A82AAE39762"
sharing:sharePointList:_array_id:/Users/admin/Public:smbDirectoryMask = "755"
sharing:sharePointList:_array_id:/Users/admin/Public:afpIsShared = yes
sharing:sharePointList:_array_id:/Users/admin/Public:smbCreateMask = "644"
sharing:sharePointList:_array_id:/Users/admin/Public:ftpName = "administrator's Public Folder"
sharing:sharePointList:_array_id:/Users/admin/Public:name = "administrator's Public Folder"
To see settings for the services use the serveradmin command with the settings option followed by the services: afp and smb:
sudo serveradmin settings afp
AFP settings include:
afp:maxConnections = -1
afp:kerberosPrincipal = "afpserver/LKDC:SHA1.978EED40F79A72F4309A272E6586CF0A3B8C062E@LKDC:SHA1.978EED40F79A72F4309A272E6586CF0A3B8C062E"
afp:fullServerMode = yes
afp:allowSendMessage = yes
afp:maxGuests = -1
afp:activityLog = yes
CIDR Conversion Table
CIDR prefix length
Dotted Decimal Netmask
Number of Classfull Networks
Number of Usable IPs
|/1||188.8.131.52||80 00 00 00||127.255.255.255||1000 0000 0000 0000 0000 0000 0000 0000||128 As||2,147,483,646|
|/2||192.0.0.0||C0 00 00 00||184.108.40.206||1100 0000 0000 0000 0000 0000 0000 0000||64 As||1,073,741,822|
|/3||220.127.116.11||E0 00 00 00||18.104.22.168||1110 0000 0000 0000 0000 0000 0000 0000||32 As||536,870,910|
|/4||240.0.0.0||F0 00 00 00||22.214.171.124||1111 0000 0000 0000 0000 0000 0000 0000||16 As||268,435,454|
|/5||248.0.0.0||F8 00 00 00||126.96.36.199||1111 1000 0000 0000 0000 0000 0000 0000||8 As||134,217,726|
|/6||252.0.0.0||FC 00 00 00||188.8.131.52||1111 1100 0000 0000 0000 0000 0000 0000||4 As||67,108,862|
|/7||254.0.0.0||FE 00 00 00||184.108.40.206||1111 1110 0000 0000 0000 0000 0000 0000||2 As||33,554,430|
|/8||255.0.0.0||FF 00 00 00||0.255.255.255||1111 1111 0000 0000 0000 0000 0000 0000||1 A or 256 Bs||16,777,214|
|/9||255.128.0.0||FF 80 00 00||0.127.255.255||1111 1111 1000 0000 0000 0000 0000 0000||128 Bs||8,388,606|
|/10||255.192.0.0||FF C0 00 00||0.63.255.255||1111 1111 1100 0000 0000 0000 0000 0000||64 Bs||4,194,302|
|/11||255.224.0.0||FF E0 00 00||0.31.255.255||1111 1111 1110 0000 0000 0000 0000 0000||32 Bs||2,097,150|
|/12||255.240.0.0||FF F0 00 00||0.15.255.255||1111 1111 1111 0000 0000 0000 0000 0000||16 Bs||1,048,574|
|/13||255.248.0.0||FF F8 00 00||0.7.255.255||1111 1111 1111 1000 0000 0000 0000 0000||8 Bs||524,286|
|/14||255.252.0.0||FF FC 00 00||0.3.255.255||1111 1111 1111 1100 0000 0000 0000 0000||4 Bs||262,142|
|/15||255.254.0.0||FF FE 00 00||0.1.255.255||1111 1111 1111 1110 0000 0000 0000 0000||2 Bs||131,070|
|/16||255.255.0.0||FF FF 00 00||0.0.255.255||1111 1111 1111 1111 0000 0000 0000 0000||1 B or 256 Cs||65,534|
|/17||255.255.128.0||FF FF 80 00||0.0.127.255||1111 1111 1111 1111 1000 0000 0000 0000||128 Cs||32,766|
|/18||255.255.192.0||FF FF C0 00||0.0.63.255||1111 1111 1111 1111 1100 0000 0000 0000||64 Cs||16,382|
|/19||255.255.224.0||FF FF E0 00||0.0.31.255||1111 1111 1111 1111 1110 0000 0000 0000||32 Cs||8,190|
|/20||255.255.240.0||FF FF F0 00||0.0.15.255||1111 1111 1111 1111 1111 0000 0000 0000||16 Cs||4,094|
|/21||255.255.248.0||FF FF F8 00||0.0.7.255||1111 1111 1111 1111 1111 1000 0000 0000||8 Cs||2,046|
|/22||255.255.252.0||FF FF FC 00||0.0.3.255||1111 1111 1111 1111 1111 1100 0000 0000||4 Cs||1,022|
|/23||255.255.254.0||FF FF FE 00||0.0.1.255||1111 1111 1111 1111 1111 1110 0000 0000||2 Cs||510|
|/24||255.255.255.0||FF FF FF 00||0.0.0.255||1111 1111 1111 1111 1111 1111 0000 0000||1 C||254|
|/25||255.255.255.128||FF FF FF 80||0.0.0.127||1111 1111 1111 1111 1111 1111 1000 0000||1/2 C||126|
|/26||255.255.255.192||FF FF FF C0||0.0.0.63||1111 1111 1111 1111 1111 1111 1100 0000||1/4 C||62|
|/27||255.255.255.224||FF FF FF E0||0.0.0.31||1111 1111 1111 1111 1111 1111 1110 0000||1/8 C||30|
|/28||255.255.255.240||FF FF FF F0||0.0.0.15||1111 1111 1111 1111 1111 1111 1111 0000||1/16 C||14|
|/29||255.255.255.248||FF FF FF F8||0.0.0.7||1111 1111 1111 1111 1111 1111 1111 1000||1/32 C||6|
|/30||255.255.255.252||FF FF FF FC||0.0.0.3||1111 1111 1111 1111 1111 1111 1111 1100||1/64 C||2|
|/31||255.255.255.254||FF FF FF FE||0.0.0.1||1111 1111 1111 1111 1111 1111 1111 1110||1/128 C||0|
|/32||255.255.255.255||FF FF FF FF||0.0.0.0||1111 1111 1111 1111 1111 1111 1111 1111||1/256 C||1|
SMB cmdlets come in two modules. Before you can really use these in powershell you first need to import them. These are called SmbShare and SmbWitness, so to import the modules:
Or for short:
Once the SMB modules are imported, we’ll start by looking at what shares you’ve got on your system using Get-SmbShare:
Next, we can create a new share with the minimum two pieces of information required and adding who get’s FullAccess, which is not required:
New-SmbShare -Name BAK -Path E:BAK -FullAccess krypted
Then we can provide a little more information if we so choose. Here, I’m going to add a description to the share I just created:
Set-SmbShare -Name BAK -Description "To be used for Windows Backup backups."
Now that we have this BAK share, we can configure who’s able to access it. To see who can access the share, use Get-SmbShareAccess along with the -Name followed by the name of each share you’re curious about:
Get-SmbShareAccess -Name BAK
Note that this -Name structure is consistent with all the smb* cmdlets.
If we want to grant another user access to our share we can go ahead and do so using the Grant-SmbShareAccess cmdlet:
Grant-SmbShareAccess -Name BAK -AccountName krypted1 -AccessRight Full
Now that I’ve given the krypted1 user access to a share, I can remove the initial user krypted since I don’t really like him any more. To do so, use the Revoke-SmbShare cmdlet, again identifying the -Name of the Share followed by the account name to remove access for:
Revoke-SmbShare -Name BAK -AccountName krypted
You can also block a user from accessing a share. If a group is granted access and the user is blocked then the user will stay blocked. To block a user, use the Block-SmbShareAccess cmdlet, identify the -Name of the share and then the users name with the -AccountName option. That krypted user is kinda’ pesky so we’ll go ahead and block him:
Block-SmbShareAccess -Name BAK -AccountName krypted
But then the krypted user ends up needing access, so we’ll unblock him using the Unblock-SmbShareAccess cmdlet with the same syntax:
Unblock-SmbShareAccess -Name -AccountName krypted
Permissions are the next most important aspect of managing access to objects. Just because a user can access a share doesn’t mean they should be able to get into that juicy morsel of a payroll directory. CACLS is the command line interface to manage permissions at the file and directory level. CACLS is not a powershell cmdlet. You can see the permissions of a file or folder using the Get-Acl cmdlet. It’s just a cmdlet that you define a location to show the permissions for. Here, we’ll check the c:SharedPayroll directory:
Then, there’s the Set-Acl command, which can alter an Acl. As you can imagine, there are a lot of different permissions that can be applied to objects, including the need for recursion and for setting the permissions for recursed objects (OK, OK – I know recursed isn’t really what you might call that, but I’ve always wanted to say it so there ya’ go!). Therefore, instead of taking you through using set-acl I’ll just say, check out the TechNet on it at http://technet.microsoft.com/en-us/library/hh849810.aspx.
Finally, many environment just want the users who can access a share to have the Acl to access the data in the shares. To aid in what should be considered a relatively simple task, you can alter an Acl by piping the output of the get-SmbShare into the Set-Acl command. This sets the Acls to be the same as the permissions set in the share itself:
(Get-SmbShare -Name Bak).PresetPathAcl | Set-Acl
I’d like to give a big thanks to Watchman Monitoring for becoming the second sponsor of krypted.com. I like the fact that thus far, I’ve managed to keep all sponsorship talks within the Mac Admin community and hope this is a trend I can continue as time goes on. I also like the fact that it’s all products that I believe in! Watchman provides an excellent service, and if you haven’t had a chance to check it out then I encourage you to do so!
As you may have noticed, we’ve been working on building some links between the App Store and patch management tools such as Casper, FileWave and Munki. We’ve been looking at policy-based management of apps as well. In this semi-new world of signing and stores and the such, there’s actually a good bit you can ascertain about an app both inside the app as well as inside metadata OS X keeps about the app. I’ve discussed signing (apps and packages) in the past, but let’s look at using some commands to help us out with some tasks.
The first command is to determine some information about apps that are on the computer. Spotlight keeps a fair amount of information about these apps and can be invoked using the mdls command. Running the command with no additional parameters looks like this (I’m gonna’ use iMovie in these examples, although note that there are spaces in a lot of app names and paths as you start scripting things – so use IFS rather than trying to use traditional array):
This results in output similar to the following (I’ve stripped out a few fields as they consume a lot of space and aren’t super pertinent to what I’m trying to do here):
kMDItemAlternateNames = (
kMDItemAppStoreCategory = "Video"
kMDItemAppStoreCategoryType = "public.app-category.video"
kMDItemCFBundleIdentifier = "com.apple.iMovieApp"
kMDItemContentCreationDate = 2011-09-28 08:04:34 +0000
kMDItemContentModificationDate = 2012-09-22 02:13:45 +0000
kMDItemContentType = "com.apple.application-bundle"
kMDItemDisplayName = "iMovie"
kMDItemExecutableArchitectures = (
kMDItemFSContentChangeDate = 2012-09-22 02:13:45 +0000
kMDItemFSCreationDate = 2011-09-28 08:04:34 +0000
kMDItemVersion = "9.0.8"
To just ask for one of these attributes, run the command along with the -name option in addition to the metadata attribute you’d like returned. For example, to see the bundle ID (kMDItemCFBundleIdentifier), use:
mdls /Applications/iMovie.app -name kMDItemCFBundleIdentifier /Applications/iMovie.app
Now, if you’d like to just quickly ascertain what apps on the system came from the App Store, use the mdfind command, along with whatever of the attributes matches what you want to know. Running mdfind for kMDItemAppStoreHasReceipt of 1 would look like the following and would result in a list of all apps on the system that came from the App Store:
Blacklisting all apps that are part of a specific category (and with regard to customer requests, that category seems to always be Games) is something we get a lot of banter about with customers. To determine this information for apps, you can run mdfind on kMDItemAppStoreCategory for Games:
You could then dump the contents of those into something that can blacklist apps (or whitelist based on other categories). Now, version control is another hot topic at various organizations. To see the version type of a given app, use the -name option with mdls kMDItemVersion
mdls /Applications/iMovie.app -name kMDItemVersion /Applications/iMovie.app
Then you can track the version of the app and take action through other ways to remove old versions and force users to upgrade. The mdfind command can also be leveraged to find apps that have escaped their traditional homes of /Applications and /Applications/Utilities, with the ability to obtain a full list by querying for kMDItemContentType of app bundles, as follows:
Loading a list of apps (output from `mdfind kMDItemAppStoreHasReceipt=1` or `mdfind kMDItemAppStoreCategory=Games`) into an array and then querying each one of them for more information is pretty trivial beyond the steps we’ve already taken. This information can then be fed into some kind of Managed Prefs script to deny or allow access to various objects or an admin could even chmod the bundle, mark it as invisible, poison it (keep in mind, if you alter it you’ll break the signing), etc in order to get some desired outcome.
You can also use defaults to read a users com.apple.storeagent.plist file for the AppleID field to see what AppleID is currently logged into the AppStore, providing another variable that can be reported on:
defaults read /Users/cedge/Library/Preferences/com.apple.storeagent.plist AppleID
And yes, it’s worth noting that users from another account or a system image, etc can be used to download apps so this one isn’t exactly certain but the purchaser isn’t stored anywhere within the bundle nor is it permissioned in a way that we can use to find the purchaser that way.
There’s still a bit of a gap right now with regards to some of these technologies that Mac SysAdmins are managing. The consumeristic technologies such as App Stores are here to stay. We’re kidding ourselves if we think that we won’t be able to buy certain apps via Volume Licenses and have pkg installers for too much longer. Apple has made no indication that they’re dropping the results that can be obtained with a simple installer command, but with forcing signing on certain objects, gatekeeper and other technologies it’s hard to say what the future will really have in store for us. Getting to a point where we can report on elements of the App Store and hopefully eventually deploy objects through the App Store should continue to help bridge these factors, but I still see the need for additional binaries from Apple to be introduced to get the rest of the way there (or at least expose a method to me so I can go in there and buy an app through the method).
I love college football. Anyone who knows me, probably knows what I’m doing about this time on a Saturday. And while I hail from the SEC, went to Georgia and have always loved “old man style” football, I’ve also lived in Southern California and now in Minneapolis where I’ve gotten to enjoy Pac 12 and Big 10 football. Doing work at Big 12 and Big East schools has also led to me attending many a game in many a stadium. I’ve also always loved watching teams that just plain suck or teams that no one has ever heard of. They have more heart than an entire division of NFL teams combined. In short, I’ll watch pretty much any football, any time.
In my travels, I’ve come across many a team who have names that just make me wonder what in tarnation they were thinkin’. So I’ve compiled a list on this beautiful college football Saturday. Here goes:
- Demon Deacons of Wake Forest: A guy in a top had rides onto the field on a motorcycle. I know, it sounds like Stan Lee in the 60′s, right. But Wake Forest is a Baptist college, so after being called the Baptists, or Old Gold and Black for a few decades, in 1923 a few people started calling them the Demon Deacons due to a fighting spirit of sorts. Given that a bunch of Baptist old timers took awhile to come around to such a name, in 1941 the Demon Deacon became the official mascot, originally being picked by one of the fraternities on campus.
- Georgetown Hoyas comes from “What Rocks” in Greek, Hoya Saxa!. Now, running around chanting Greek isn’t probably what most people think of a ruckus college crowd these days, but this name goes all the way back to 1893! Their mascot is a bulldog, so I’ve always had a soft spot for ‘em.
- Stormy Petrels is a name I don’t know that I’d of heard if I weren’t from Georgia. This is the name of of the Oglethorpe University team and comes from a seabird. It came by the way of a college president in 1915 and supposedly dates all the way back to James Oglethorpe, the founder of the Georgia colony.
- Boll Weevils are the number one enemy of cotton. And if you’ve ever opened up some flour filled with these little devils then you might get totally squeezy seeing an 8 foot tall one roaming the sidelines of the University of Arkansas at Monticello. A great name for a team in 1920, when they got the name. The women’s teams are known as the Cotton Blossoms. Makes you wonder what exactly what the big industry is in that area…
- Hokies is the name of the team out of Virginia Tech. They’re not having a great season, but they have been pretty darn good ever since a guy named Michael Vick went there. The name means nothing, except for to millions of college football fans.
- Tar Heels is the name of the North Carolina team. I’ve been unable to ascertain where the name originated, but Walt Whitman did call North Carolinians tarboilers, so I’ll go with people that were unlucky enough to step in tar. The Hokies and the Tar Heels are both in the ACC.
- Anteaters of University of California Irvine. This name isn’t over 100 years old, but it is closing in on 50 years old. The name was chosen by students, soon after the school was founded, in 1965.
- Ichabods of Washburn University in Kansas are named after college a headless horseman. Actually, they aren’t. The name hails from the founder of the school, Ichabod Washburn. But don’t tell the guys on the other side of the lines that!
- Wonder Boys of Arkansas Tech were named in 1919. Guess things were different back then… These days, just think the guy who plays Iron Man also played a Wonder Boy.
- Horned Frogs is the name of a team that I’ve always liked, Texas Christian University (TCU). Now, there are a lot of awesome things you can do with the name of this team, but to keep it PG I’ve always just called them the Horned Toads.
- Trolls is the name of the Trinity Christian College team, in Illinois. Irony is that they’re not very Christian beasts. Named in ’59, they were already out of all the good names by the time he got to town…
- Cornhuskers is the name of the teams at the University of Nebraska. I have loved watching them over the years and they’re probably one of the biggest names on this list. The reason I put them on here is that if you think about it, people who husk corn is a weird thing to name a team after… Of course, to continue picking on the Big Ten, so are Buckeyes and Golden Gophers. Then again, you’d expect funny names for teams in a conference where they haven’t learned to count past 10 (there are 12 teams in the Big 10).
- Hoosiers are the University of Indiana and a term in fact used to refer to those from Indiana. To continue picking on the Big 10, this term also has no real known origin but dates back to the 1830s before football was awesome. So there ya’ go. It’s funny, many of these names sound weird if you’ve never heard them but if you watch sports they just seem second nature, like they belong…
- Billikins is the name given to teams of St Louis University. Billikins are elven charm dolls. Now, if you’re Tigg from Sons of Anarchy and you see one of these, you might just run off the field screaming. So if you play football against big burly bikers then hey, great name!
- Cobbers is the name of the team at Concordia University. Apparently corn is somehow linked to football.
- Fighting Artichokes is the name of the Scottsdale Community College team. ‘Cause nothing strikes fear into carnivorous football players more than the thought of having to eat a thistle!
- Aggies is the name of the Texas A&M team (that just beat the #1 ‘Bama Crimson Tide tonight). This isn’t actually a weird name once you wonder and realize it’s short for Agriculture, the A in the name. The Aggies are part of the Big 12, by the way. A conference that doesn’t have 12 teams. TCU is also in the Big 12 now, although it’s their 3rd conference in as many years…
- Jumbos of Tufts University are not named after 300 pound lineman. Instead, they’re named after an elephant donated by Barnum after it died and got stuffed by taxidermists. I guess not everyone can name their team the Crimson Tide and then have a picture of an elephant, right… Anyway, I put this on the list ’cause it makes me think of the movie Dumbo. That’s all…
- Geoducks (geo is pronounced gooey) is the name of the Evergreen State College (Washington) teams. I now know that a Geoduck is the largest burrowing clam in the world. Their mascot dresses as a mollusks which must be terrifying for opposing teams that have shellfish allergies. “Go, Geoducks, go, Through the mud and the sand, Let’s go. Siphon high, squirt it out, Swivel all about, Let it all hang out.”
- Fighting Camels is the name of the Campbell University team. But the name of the school or team isn’t why they are on this list as much as the name of the mascot. Here he is:
- Scrotie is the unofficial mascot of the Rhode Island School of Design. This isn’t a team name. But they have the hockey team called the Nads and the basketball team named the Balls. I’ll let you google image the mascot yourself and spare you the imagery here…
- Fighting Pickles is the name of the North Carolina School of the Arts teams. It’s an art school… But you’d be surprised how similarly their pickle looks like Scrotie above!
- Dirtbags is just an awesome name. And very Long Beach in some ways. There’s not much more to say about California State University-Long Beach.
- Banana Slugs is my second most favorite name weird name around. If you’ve ever been to Santa Cruz, you probably understand why marijuana was legalized in California. If so, then this name makes sense; otherwise, not-so-much. Trivia: in 1985, the administration wanted to name the team the sea lions. The students, high though they may be, ended up winning out and the Banana Slugs it was!
- Ragin’ Cajuns is probably my favorite of these. Louisiana-Lafayette is Cajun country and the name of this team dates back to the 1970s, although they’ve been playing football since 1901.
Runner ups, dropping out of the top 25 for one reason or another: Black Flies, Pomona Sagehens (The Huns was an awesome name), Gorlocks (named from Gore and Lockwood, two streets that intersect, their mascot is actually a cheetah/buffalo/St Bernard mix that would make Napoleon Dynamite totally jealous), the NYU Violets, the University of New England Nor’easters, Chaparrals, Chanticleers, Lemmings, Poets, Squirrels, Thundering Herd (I’m guessing the only Buffalo in Huntington West Virginia is the Buffalo Wild Wings on 4th), Ladies and Gents, University of Delaware Blue Hens, Student Princes, the Hustlin’ Quakers of Earlham College, Sooners (I picked on the Big 12 too much already), Tulsa’s Golden Hurricane, the Zips, the Lutes (no really, another Christian school, too), Shockers (whoever thought up WuShock was certainly struck by lightning), Terrapins (ya, nothing says we average 8 days for a 40 yard dash like the Terps), the Boilermakers (I picked on the Big 10 too much already), the Green Terror, the Keelhaulers, the Gamecocks (the baseball caps they sell at the campus store just say COCKS), the Bridges (I guess it is Brooklyn after all), the Fighting Koalas, the South Dakota School of Mines HardRockers (didn’t they beat Minnesota a couple of years ago along with everyone else in the Dakotas?!?!), the Lord Jeffs (srsly?), the Okras (okra scares the crap out of me) and of course, any team with a Swallow for a mascot (college, pro, etc).
Note: I’ve tried to leave out any teams named after Native American tribes.
Now that I’ve probably managed to offend pretty much every sports fan, I’ll tell you that I love these names. I didn’t call this article the “25 Dumbest Names for College Teams” or the “25 Stupidest Names in College Sports.” There’s a reason for that. I love all these teams. And honestly, it would seem somewhat trite for most of these teams to be called the Bulldogs, the Falcons, the Braves, the Hawks, the Thrashers, the Georgia Southern Eagles, the Valdosta State Blazers or the Mercer Bears. But if you’ve had a name for decades then you kinda’ stick with it, trite, silly or awesome. Now, let’s go get some Fighting Pickles tats!
There are four ways to create groups in Mountain Lion Server. The first is using the Server app, the second is using Workgroup Manager, the third is using the Users & Groups System Preference pane and the fourth is using the command line. In this article we will look at creating groups in the Server app.
Once a server has been an Open Directory Master all user and group accounts created will be in the Local Network Group when created in Server app. Before that, all user and group objects are stored locally when created in Server app. Once promoted to an Open Directory server, local groups must be created in Workgroup Manager, the Users & Groups System Preference pane or using a command line tool appropriate for group management.
- Give this group a shared folder: Creates a shared directory for the group, or a group with an ACL that grants all group members access.
- Make group members Messages buddies: Adds each group member to each other group members buddy list in the Messages client.
- Enable group mailing list: Enables a list using the short name of the group where all members receive emails to that address.
- Create Group Wiki: Opens the Wiki interface for creating a wiki for the group.
Once changes have been made, click Done to commit the changes.