Set EFI password on clients from Snow Leopard Server?

Hi everyone,
I would like to know if there is a way to set up EFI password over my 10.6 clients without use of an installation DVD. I have about 500 clients here and it will become a great loss of time set them one by one booting from DVD.. They are managed by a 10.6 server and soon I'll receive an ARD license.
Thanks in advance

Thanks very much.
Following your tip I've found that to enable password request the command is
sudo nvram sucurity-mode=command
followed by
sudo nvram security-password=<pass_code>
this sets a chosen password. To know the encoded version of our pass is sufficient use
nvram security-password
Now i'm looking for a way to reset both theese parameters for a rollback procedure.

Similar Messages

Can I image Lion clients from Snow Leopard server using SIU?

I have a new iMac Lion client I need to image to a number of machines, using Snow Leopard Server, but System Image Utility will not recognize the Lion client as a valid source volume? Has anyone else experienced this yet?

Images must always be created on the same OS.
You'll need to download the Lion Server Admin Tools onto one of the clients and make it your "imaging system".
http://support.apple.com/kb/DL1419

Complications migrating from Snow Leopard Server to Mountain Lion Server.

I'm migrating from Snow Leopard Server to Mountain Lion Server. The article "OS X Server: Upgrade and migration" (http://support.apple.com/kb/HT5381) says
"Make sure that any DNS or DHCP servers on which your server depends remain running during the upgrade"
This advice is reinforced by the details of the article "OS X Server: Steps to take before upgrading or migrating the Open Directory database" (http://support.apple.com/kb/HT5300).
As the server I'm migrating from provides these services it will need to be running during the migration process. This would seem to limit my options to doing the migration from a Time Machine backup (or, making a seperate clone of the server's drive and connecting it externally to the new box)
My main concern is the seemingly inevitable clash that is going to occur on the network as the new server takes on the roles of the old one - while it is still running.
What are my options here ?
This is my second attempt as on my first try I did the migration from the TM backup with the network down - and none of my local network users or their home directories were migrated, although the settings for the mount points were, but there were no actual directories where they pointed to!
Clear directions on how to procede would be VERY MUCH appreciated
Thank you.

Moving from Snow Leopard to Mountain Lion means first installing the client (non-Server) version of Mountain Lion and then install Server.app this means that for at least part of the process you will not be running DNS, DHCP or Open Directory.
If you are going to end up using the same DNS name and IP address after the change then an approach you could follow would be as follows.
Destroy any Open Directory replicas
Archive your Open Directory Master (to make a backup)
Note down your DNS records in case they get messed up
Export via Workgroup Manager your users, and groups (you might not need this but better safe than sorry), make sure you do not include the diradmin account
Keep a full back of the server (you should always have backups)
Note down your DHCP server settings in case they get messed up
Note down any other service settings
Install Mountain Lion
Install Server.app
Install Workgroup Manager (extra free download)
Run Server.app
Make sure settings for services are as much as possible the same as before
If your lucky that may be all you need to do, otherwise...
Restore Open Directory archive, if your lucky that will be all you need to do, otherwise...
Make new Open Directory Master
Run Workgroup Manager
Import users and groups you previously exported
You will then have to set passwords for each user as these are not preserved via Workgroup Manager export
When I did this, I was also being forced to change all my IP addresses so I had no choice but to use Workgroup Manager to export and import accounts.

Upgrade from Snow Leopard Server to Lion Server hangs at configuring services...

I am running the Mac mini with snow leopard server 2.53 ghz 2GB of ram, 2x500GB hard drives, and have followed through the process to install Lion Server. The installation appears to be hung at the Configuring Services section of the setup process. I have left it for a couple of hours and nothing has progressed.
Should I leave it longer, hoping that it will work through the process (if in fact it is working through something)?
How long should this normally take?
As this is my work server, hosting mail, web, FTP, and file sharing, it is rather important to get it up and running as quickly as possible.
Any thoughts on how I can get it moving?
Hard power off of the Mac Mini reboots the machine, then proceeds back to the setup page, and then hangs on the same Configuring Services.
Any assistance would be much appreciated.
Thanks.

Lion Server Upgraders,
beware and proceed with caution.
Apple web site is naively optimistic on the upgrade process:
"To upgrade your Mac to OS X Lion, you don’t need to drive to a store, bring home a box, and install a bunch of discs. All you do is click the Mac App Store icon, buy Lion for $29.99, and your Mac does the rest. Just make sure you have what you need to download Lion to your Mac."
And then has a 3 step process...
This is completely miss leading.
Read this document first: http://manuals.info.apple.com/en_US/lion_server_upgrading_migrating.pdf
It will make it readily apparent that moving from Snow Leopard Server to Lion is not going to be simple.
Having done this twice now.. I have found that:
1. Open Directory migration is a weak point. Lion & Snow Leopard Open Directory are not compatible, so if you have masters & replica then expect trouble. I have an unresolved issue trying to get a simple Lion Server to Lion Server Open Directory replica up and running. This compatibility seems to also cause migration to fail, as I found that all my local User/Groups transferred ok but non of the /127.0.0.1/LDAPv3 (Open Directory) ones did. This is a very important item, as all the mail accounts in dovecot use LDAP generated UID, so you have to be careful that you do not loose mail accounts.
2. Mail - your mail aliases will not transferred, so you will need to reapply the aliases.
3. Web Server Setup - This broke, under migration as I gather the entire Web serving tree has changed. In particular I had "Snow Leopard" Web Mail (which is based on Squirel) on my "Snow Leopard" Server and this is now dead...
4. Digital Certificates - I found that the valid (ie signed by trusted CA's) did not get migrated, so I had to re-imported my Digital Certificates. If you have paid for third party CA certificates then make sure you have got these copied somewhere, as if you loose them then you will likely need to go to your provider and get a certificate revocation and new certificate, which will cost you money!
Cheers,
Zebity.

Upgrade from Snow Leopard (Client) to Snow Leopard Server

Hi,
can I upgrade from Snow Leopard client (10.6.3) to the Server (10.6.3) without having to reformat my disk and delete all the apps etc?
Thanks

Hi Michele,
Upgrading from 10.6 to 10.6 Server is unfortunately not possible without an erase and install of the Server OS.
If you want to preserve your Client OS initially, you could split the primary disk partition and install 10.6 Server on the other partition, then remove the Client OS partition when ready and reclaim the disk space for the Server partition.

Error configuring services from Snow Leopard Server to Mountain Lion Server

I am trying to upgrade a Snow Leopard Server Mac Mini to Mountain Lion Server.
We have two Mac Mini servers at our office (production and backup) so I migrated the everything from our production server to the backup using the migration assistant when setting up the backup computer.
I now have the backup at home trying to upgrade it to Mountain Lion Server. I have downloaded and installed Mountain Lion as well as the Server App version 2.2. I basically followed the simple directions found in the Apple documentation.
I started the server app and it got to the part where it said "Upgrading services". After running for a few minutes, I get a window that states "An error occurred while configuring your server." It also sayd "The following actions failed or were not attempted:" with a red dot next to "Upgrading services". The other three items: "Authenticating to local directory", "Reading directory configuration" and "Authenticating to local directory services" have gray dots so I'm sure they were not even attempted.
Our Snow Leopard server is setup for SMB file sharing, LDAP services, FTP, Web, DNS, DHCP.
Can someone point me to where I can figure out what exactly is failing? Are there specific log files I need to look into?
Thanks

Have EXACTLY the same issue - also tried reinstalling mountain lion server fresh and still had the same problem...

Server Admin. file sharing lion client to Snow leopard server

I'm running Lion on my client Mac and my Server is Snow leopard 10.6.8. I have to use Server Admin 10.7 on Lion but there is no "File Sharing" tab to set up or edit the file sharing options on my 10.6 server?. I understand this is correct for Lion Server, but how do I get round it for Snow leopard Server?? On the Apple website compatibility page (http://support.apple.com/kb/HT1822) it states:
"Mac OS X Server v10.6
To administer a Mac OS X Server v10.6-based server, you can use the Server Admin Tools 10.6 on a Mac OS X v10.6 (client) computer. You should match the version numbers of the server, tools, and admin workstation as closely as possible; for example, use Server Admin Tools version 10.6.8 on Mac OS X v10.6.8 to administer Mac OS X Server v10.6.8. You may also use the Server Admin Tools 10.7 on an OS X Lion computer to administer Mac OS X Server v10.6."
So, How do I administer file sharing???

To configure File Sharing on a 10.6 server using 10.7 Server Admin, click the service (AFP, SMB, NFS, etc.) then click the Share Points tab.

RSS feed from Snow Leopard server

I want to host an RSS feed from my server. What settings would be necessary to accomplish this?

The first things to do would be to download a program that will maintain your RSS feed. Podcast spitter from the app store was the top hit when I did a search. I've not used it, but it appears that it'll do the trick.
Next, just create a website using the web service in Snow Leopard Server.
Point Podcast Spitter at the share that hosts your web site and that should do the trick.
When you upload your RSS feed, all the stuff needed to make it an RSS feed should go with it.
Granted it's a VERY thinned out version of the steps needed to take, but the concepts are correct.
If you need a more detailed description, write back with more info about how your server is set up and how it's connected to the internet.
HTH
-Graham

Tiger PPC clients with Snow Leopard Server

I installed Snow Leopard Server (10.6.4) on an XServe.
DNS - AFS - DHCP are set up correctly and have been checked several times.
Clients have an AFP automount for network home directory. This share point is set up correctly as well and has been checked by Server's gurus.
Everything is fine for Leopard clients but when it comes to connect to the Server with Tiger clients (PPC 10.4.11) something strange happens :
- the first connection is correct and the home directory mounts normally
- when the user disconnects and tries to connect a second time the folder home directory is not mounted and therefore the user can't have access to his/her home
- although it's possible to mount the folder home directory using the "Connect to server…" command and then choose the user's home directory folder this isn't very handy with young students
I have done extensive researches on Apple's documentation and on the forums but nobody seems to mention such a problem.
Any idea what's wrong ? Already encountered the same issue ?
Any help would be appreciate

We have reported an automount bug which "may" be related to your problem to Apple. Our symptoms occurred in Leopard 10.5.8 and also in Snow Leopard 10.6.2 and resulted in user's seeing a message "You are unable to log in to the user account <account> at this time." This was due to an apparent problem in Mac OS X when reusing a share via automount.
In our case we found that the period of time during which login is denied can be reduced by editing the file /etc/autofs.conf on the Mac and reducing the value of AUTOMOUNT_TIMEOUT.
Hope this helps.

Lion clients with Snow leopard Server

Are there known issues with a Snow Leopard Server Mananging Lion Clients. I currently manage 40 IMacs in two labs
all running Snow Leopard, the only services I use on the Mac Server are Open Directiory, Print Services, AFP, and FireWall services
the Server is a Mac PRo with 2x3.2 Ghx quad-Core Intel Xeon Processor and 32. GB RAM

Snow Leopard can't serve AFP devices to Lion clients out of the box. There seems to be a workaround, but I haven't gotten it working myself yet.

Downgrade from Snow Leopard Server to SL (non-server)

Is that possible to downgrade from SL Server to SL without making a clean install ?
I've just bought a standard version of Lion and I can't install it...
Thanks

Hi
You can't install Lion Server (which is simply the Server App) without installing Lion anyway. What this means is you can install 'ordinary' Lion on your existing Snow Leopard Server and provided you don't download and launch the Server App your Snow Leopard Server won't really be a Server anymore. Leastways not with any usuable 10.6 Server Administration applications (Server Admin, WorkGroup Manager etc) that you can use as these are all deleted/removed when Lion is installed.
HTH?
Tony

Upgrade path from Snow Leopard Server to Lion Server

Just curious what the method is for upgrading a server currently running snow L. to Lion. Do you just buy the app and install? Will everything "reboot" exactly as is was? (Users, groups, share points, security settings, firewall, etc)
As you can imagine any changes to a server in an office environment can be stressful.
Also if anyone has successfully upgraded their servers to Lion and has feedback I would appreciate it.
- C42D

Hi there,
I would wait a little to have the early bugs in both OS X Lion and OS X Lion Server sorted out.
One common upgrade path i follow :
- Backup system disk
- Backup data disk
Why save both disk for an upgrade (as you already backup the data disk don't you ? ) and not only system ?
Imagine that once you update your server to OS X Lion Server, it updates some data too (mail database and so on) and you want to go back to OS X Snow Leopard Server...that would render your data unusable !
Regarding OS X Server in general:
- Backup Open Directory
- Backup Services configuration
Hope that helps

NetInstall image not installing on Mac Pros from Snow Leopard server

Using the System Image Utility, I created a NetRestore image from the Mac Pro machine that was configured in the way that we wanted it (applications, etc.). I copied this image to the server (Server HD 3), and configured in Library/Netboot/NetBootSP0. The image is in Base Image.nbi, and I have NetBoot set up in serveradmin. I have this set up in the images tab in NetBoot:
Default is checked;
Image Name: Base Image;
Enable is checked;
Diskless is not (we're wanting to 'restore' this image on all 17 MacPros)
Index is 2323;
Arch is Intel;
Protocol is NFS.
Comment box info:
Storage Volume: Server HD 3
Kind: Mac OS X NetInstall (Intel)
Language: default
Description: NetRestore of Mac OS X 10.6.2 (10C2234) Volume.
Type: NFS.
When I go to one of the other computers, go through system preferences and select the "Base Image" to restart from, I get a gray screen; then the globe flashes, and then the machine will go to the local hard drive to start up.
The reason I went to a NetRestore image was because the system image utility would not create a netinstall (greyed out) from a volume.
Is there something I am missing here?
Message was edited by: smaugg

So glad its you Mr. Hoffman - your guides are most helpful - thank you so much for what you do.
I did some digging and found out that since im running CS4 and that it trys to run on 64 bit mode but my Lion system and most folks systems I guess are in 32 bit mode - i had to down load some 32 bit Adobe Unit Types from Adobe and replace the ones on my system - restart - and bingo - im no longer getting those errors - see this link where i found this work around:
http://kb2.adobe.com/cps/516/cpsid_51615.html
That fix cleared a lot of the junk that adobe was doing but i am still getting error 1101 - see below
11/26/11 2:36:37.298 PM opendirectoryd: peer appears to be running Mac OS X 10.6 or earlier
11/26/11 2:36:37.298 PM opendirectoryd: got error 1101
Any idea what this is ?

Setting up a Home Network w/ Snow Leopard server

I would like suggestions on how to best configure a home network.
One of my main goals is to enable my 5 kids to share 3 computers and my mini server.
I would like them to each have an account with the same files and set up available on each computer.
My wife and I also have laptops connected to the network.
My computers are listed below.
I have Airport extreme and some external hard drives also.

jpadilladeborst wrote:
Is it advisable to use the same Hard Drive that the server is running off as a sharepoint?
It doesn't matter too much - the only issue is from a restore point of view - what will you lose if the server creams in? From that perspective, it probably makes sense to have the OS on one drive and the 'shared area' (if that's what you're going to do) on the other drive. Then, once you have everything set up and working how you like, use Disk Utility or CarbonCopyCloner or something similar to image the OS drive onto an external HD for speedy restore purposes, and maybe set up Time Machine on the server itself to back up the shared area and probably the /Users/ directory to another external drive - 1TB+ if you have it.
Remember that in order for the drive to be useable as a TM destination, it has to be formatted in a way that OS X can understand, so GUID partition table and probably Mac OS Extended (Journaled). The reason I point that out is that some NAS drives (you mentioned a Hip something or other which I'm not familiar with but may fall under this category) run their own partition tables etc, sometimes even running their own OS (which can be Win 98 or similar) thus rendering them useless from this point of view.
Other things to think about are how you're using your space. Remember that if each user account has iTunes with a load of songs, that is going to suck up space on your server very quick. If that's the case, perhaps consider dumping everyone's songs onto a sharepoint and setting that as the iTunes storage location for each user's iTunes. Alternatively, with iTunes 9 you can now share music libraries between multiple computers (providing they're all using the same Apple ID). Of course that throws up iPod/iPhone syncing problems, so keep it all in mind.
Furthermore (I think you've already mentioned this), see what you can put on the shared area instead of in users Documents folder. For example, if one of them has a load of family photos - put them all on the shared area. Stuff you don't want the kids to have access to (financial documentation etc) can still be put on the shared area, but can be protected with user account-based permissions (this is where server OS's and networked user accounts really come into their own), or just leave within one user account.
And for goodness sake, especially if you have things you don't want the kids to have access to, don't let the main server account be the one that the kids use to log on to the server for every-day purposes, since they will then have access to everything (since the main admin account on any mac is by default 'root', which means it is the account which is allowed to do absolutely anything to an OS, including changing permissions etc etc)

Migrating from Snow Leopard to Mountain Lion Server

Hi all. I kinda drop in and out of this forum, mostly when I've got a puzzler that I can't figure out. My journey from Snow Leopard to Mountain Lion was a little slow. I tried to make the transition from Snow Leopard to Lion and failed, but this time I made it and I thought I'd share a little scratchpad post I wrote to document what I did. Mostly this is about adding back a few things that I really need. Here's the list of stuff that I added back:
Firewall management (IceFloor)
MySQL
Webmail, email filtering rules and email aliases (RoundCube)
"Group" emails (short, multi-recipient email exploders)
Mailing lists (Mailman)
I also dramatically improved reliability by adding a lot of memory, and doing nightly-restarts of the machine.
Here's a link to the post
http://www.haven2.com/index.php/archives/migrating-from-snow-leopard-server-to-o sx-server-mountain-lion
I'm happy to report that the new server has been running for a month or so and all seems fine. Whew. A long journey. Thanks to all of you who posted things that helped me along the way. Hopefully this will return the favor.

Moving from Snow Leopard to Mountain Lion means first installing the client (non-Server) version of Mountain Lion and then install Server.app this means that for at least part of the process you will not be running DNS, DHCP or Open Directory.
If you are going to end up using the same DNS name and IP address after the change then an approach you could follow would be as follows.
Destroy any Open Directory replicas
Archive your Open Directory Master (to make a backup)
Note down your DNS records in case they get messed up
Export via Workgroup Manager your users, and groups (you might not need this but better safe than sorry), make sure you do not include the diradmin account
Keep a full back of the server (you should always have backups)
Note down your DHCP server settings in case they get messed up
Note down any other service settings
Install Mountain Lion
Install Server.app
Install Workgroup Manager (extra free download)
Run Server.app
Make sure settings for services are as much as possible the same as before
If your lucky that may be all you need to do, otherwise...
Restore Open Directory archive, if your lucky that will be all you need to do, otherwise...
Make new Open Directory Master
Run Workgroup Manager
Import users and groups you previously exported
You will then have to set passwords for each user as these are not preserved via Workgroup Manager export
When I did this, I was also being forced to change all my IP addresses so I had no choice but to use Workgroup Manager to export and import accounts.

Set EFI password on clients from Snow Leopard Server?

Similar Messages

Maybe you are looking for