ARD to set root password

Is there a way to set the root password to several clients using ARD 2.2? I would normally do this using Netinfo Manager at the machine. I'm assuming there is a unix command to do this?
I finished setting up a computer lab and forgot to set the root password before I cloned the hard drive. I need to secure my workstations from clever students.
Thanks for any help.

found answer http://support.apple.com/kb/HT1528

Similar Messages

How to set root password apple manual steps not correct

When I follow the steps Apple has for setting the root password and I click login options I don't see a button that says Open Directory Utility? Any suggestions?

found answer http://support.apple.com/kb/HT1528

Cannot set root password

I just installed "Don't Panic". The install seemed to go OK, but when I attempt to set the root password I get the message
passwd: Authentication token lock busy
I would appreciate information on how to do this.

Problem resolved. It must have been a glitch in the original install as a reinstall solved problem.

OEL 6.1 -- How to set root password?

Hi all,
Maybe it's a silly question, but I'm new to OEL, and this 6.1 install is the first time I've installed OEL.
Everything seemed to go perfectly smoothly, but the installer never prompted me to enter a root password, and now I've got a system that boots to a login prompt, but I have no idea what userid/password to use to login. Is there a default root password?
Help!
Thanks,
-Mark

Dear mbobak,
You don't need to boot into rescue image, mount, chroot
all what you need is to boot into single mode from GRUB.
If it happen again, please follow these steps:
- Reboot the system and wait for the GRUB screen to appear
- Highlight the kernel version you're currently using (usually the newest version) from the GRUB list
- Press "e" to be taken to the boot commands edit screen, highlight the line which starts with kernel and press "e" again
- Add "single" to the end of the line, so it will look like this:
kernel /vmlinuz-kernel-version ro root=LABEL=/ rhgb quiet single
- Press "Enter" to save the changes
- Press "b" to boot in single user mode.
Your system will begin loading and, at some point, you will be presented with a root bash prompt.
- In the new prompt type passwd and choose a new password for root.
- When done, type reboot to restart the system. After reboot, GRUB will be back to normal so no further modifications are required.
Reference
http://news.softpedia.com/news/Resetting-a-Forgotten-Root-Password-40544.shtml
Regards

Error when creating root password during arch setup.

This has happened 3 times after I've recustomized everything. I get:
/arch/setup: line 1506: /usr/sbin/chroot: Input/output error
Until it covers the screen then I have to cancel the operation and reload setup.
I searched and cannot find any answers to this problem.
Last edited by ikithme (2008-10-07 06:55:27)

Have you tried skipping the 'set root password' part?
You can set it later.

How to enable root on mac on 10.9.2 and how to set the password for the same ?

how to enable root on mac on 10.9.2 and how to set the password for the same ?

http://support.apple.com/kb/ht1528
Follow the steps for Lion.
But, why are you doing this? I've never found the need to do that.

Setting restrictions on minimum characters for root password

Hi,
I didn't think this could be that hard. I changed /etc/default/passwd and PASSLENGTH=8. I assumed this would mean if I reset the password of root I would need to specify a minimum of 8 characters. This is not the case. I was able to set the root password to lk.
Can somebody tell me how I do this?
Thanks

I believe that the restrictions are only for non-root accounts.
Darren

How to Delete and Reset a Lost Root Password on a System With a Mirrored ??

hi All,
we are experiencing problem,lost root password on Solaris 10 Sparc T5120, with mirror root,
and we found the solution from Metalink.oracle.com, has anyone have try this??
here list capture the file system :
Filesystem size used avail capacity Mounted on
*/dev/md/dsk/d10 2.0G 349M 1.6G 18% /*
*/dev/md/dsk/d40 9.8G 563M 9.2G 6% /usr*
*/dev/md/dsk/d30 9.8G 1.4G 8.4G 15% /var*
*/dev/md/dsk/d50 7.9G 310M 7.5G 4% /opt*
*/dev/md/dsk/d600 3.8G 4.3M 3.8G 1% /home*
*/dev/md/dsk/d602 471M 20M 404M 5% /app/controlm*
*/dev/md/dsk/d601 471M 251M 173M 60% /app/ctsa*
*/dev/md/dsk/d604 4.9G 1.1G 3.8G 23% /app/oramon*
*/dev/md/dsk/d603 20G 11G 8.2G 58% /app/oracle*
*/dev/md/dsk/d606 39G 10.0G 29G 26% /proj/iprdb01/orafra/iprod01p*
here the step :
Solstice DiskSuite[TM] Software: How to Delete and Reset a Lost Root Password on a System With a Mirrored Root Disk [ID 1010755.1]
Solution
Steps to Follow
How to delete and reset a lost root password on a system with a mirrored root disk.
1) Insert the Solaris[TM] Operating System CD-ROM into the CD-ROM drive.
2) Once the CD-ROM is in the drive, perform a stop-a. This brings the system down to the "ok" prompt.
3) From the "ok" prompt, perform a single-user boot from the Solaris OS CD-ROM.
ok boot cdrom -s4) At the "#" prompt, determine which disk is the system's boot disk (containing the root file system). There are several Oracle architectures and various configurations of systems when it concerns a boot disk. As a general rule, most boot disks are attached to controller 0 (c0). Usually, their SCSI target is
either 3 (t3) or 0 (t0). However, Oracle machines are very flexible, and the boot disk could be at a different location. If you are not sure which disk is your boot disk, perform the following steps to determine the location of the boot device:
a) # eeprom boot-device
The output might appear to be simple, such as "disk" or "disk1" or more complicated, such as a pathname "/iommu/sbus/espdma@4,8400000/...../sd@3,0:a".
b) Make note of the boot-device. If the boot-device is a pathname, it is beyond the scope of this information to provide the location of the customized boot disk. However, for most configurations,
finding the customized boot disk is an easy task. The "Format" command shows all available disks:
#format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
(enter its number): c) Enter d to exit format.
Now, you will have an idea what disks are on the system. Therefore, if the boot-device is "disk" and format shows "c0t0d0" (on some systems "c0t3d0") then that is the boot device. If boot-device
shows "disk1" and format shows "c0t1d0," then that is the boot device. If format shows multiple disks, then based on what the "eeprom boot-device" command shows, the system's boot disk would be:
boot-device format
disk c0t0d0 or c0t3d0 (machine dependent)
disk1 c1t0d0
disk2 c0t2d0
disk3 c0t3d0 or c0t0d0 (machine dependent)
and so on ....
5) Because the system was not brought down gracefully (no root password means having to use the Stop-a keystroke to "crash" the system), you need to run "fsck" to clean the root partition (slice). The fsckalso confirms that you selected the proper slice.
# fsck /dev/rdsk/c1t0d0s0
where the X and Y are determined by the previous procedure. It is also possible to have a root partition which is not on slice 0 (s0), but, again, that is not a standard configuration.
The output of "fsck" looks like this:
** /dev/rdsk/c1t0d0s0
** last mounted on /
** Phase 1 .....
The second line in the output of "fsck" ("** Last mounted on /") confirms that this is the correct root filesystem partition. Answer "y" to any questions fsck asks. There shouldn't be too many items
needing repair. If there are, there is a possibility of a corrupted root filesystem. After fsck is finished, mount the root partition:
# mount /dev/dsk/c1t0d0s0 /a
Again, X and Y are the same as for the fsck command.
For example:
# mount /dev/dsk/c1t0d0s0 /a
6) From the root prompt, set the proper TERM type command (such as vt100, dtterm, sun, and so on)
by entering this command:
# TERM=sun; export TERM
7) Use the VI text editor to edit the /etc/shadow file:
# vi /a/etc/shadow
8) The first line of the /etc/shadow file is the one you want to modify.
It looks like this:
root:c3.yAVmYodWsc:6445::::::
9) Delete every character between the first and second colons in the first line of the file. When you finish deleting the characters, the line should look like this:
root::6445::::::
10) Press the Escape key, then enter the following to save the file and exit vi:
:wq!
11) Use the VI text editor to edit the /etc/system file andremove the "rootdev" line shown below:
# vi /a/etc/system
*rootdev:/pseudo/md@0:0,0,blk
Don't comment out the "rootdev" line. Actually remove it.
12) In the /a/etc/vfstab file, replace the lines for the system filesystem meta-devices with their underlying partitions. For example, change lines from
/dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no -
to
/dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no -
ONLY change the lines for root (/) and the filesystems that were affected by the actions you took in step 1 of this procedure. All other metadevices may stay as is in this file.
13) Unmount root, check the root filesystem, and then stop the system:
# cd /
# umount /a
# fsck /dev/rdsk/c1t0d0s0
# stop-a
14) Boot to single-user mode:
ok boot -swTHIS STEP IS VERY IMPORTANT; YOU MUST BOOT TO SINGLE-USER MODE TO AVOID FILESYSTEM CORRUPTION.
If the system does not boot to single user mode, you might have made a mistake in the previous steps.
15) Because the root password was cleared in an earlier step, press Return when prompted for the the root password. Once you are in single-user mode, you must clear the metamirrors and all the sub-mirrors for the root filesystem. For example, if root (/) is d0, run the following command:
# metaclear -f -r d0
Running the metaclear command not only clears the metamirror but also clears the submirrors that are part of this mirror.
16) When the metamirror is cleared, continue the boot up to multiuser mode by either pressing CTRL-D or by entering the following:
# exit
Now everything should be as it was, except that the system partition is on the underlying partition and isn't mirrored. You will simply need to re-create the metadevices for the root mirror as you had originally.
many thanks

Hi,
Halt your machine.
Boot with fail-safe mode.
format and list out the disks. (You can get the root & mirror disk (c#t#d#) details from /etc/lvm/md.tab of your root or mirror disk. Earlier explorer output may help)
Mount the root disk and remove the password entry in /etc/shadow
umount it.
Mount the mirror disk and remove the password entry in /etc/shadow
umount it.
reboot the server.
Hope this helps!

Reset lost root password and now have read only filesystem

Hello,
I have recently had to reset a locked root password by booting from cdrom, mounting the first boot disk, editing the shadow file to remove root's password and rebooting the system.
The system has booted OK but, I now have a read only filesystem - everything in / cannot be edited, passwd doesnt work etc.
df -k shows the root (/) filesystem has been mounted on the physical disk I edited:
Filesystem kbytes used avail capacity Mounted on
/pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a 10085836 185862 9799116 2% /
but in the vfstab it still references the disksuite metadevice:
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
/dev/md/dsk/d30 /dev/md/rdsk/d30 / ufs 1 no -
So, can I simply boot from CDROM again, amend the vfstab to be /dev/dsk/c0t0d0s0 (instead of /dev/md/dsk/d03) and reboot?
Any help with this is appreciated!
Thanks,
Emma

df -k should have shown root mounted on md0
e.g. on my machine
# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d0 8260691 4366317 3811768 54% /
what does /etc/system show for rootdev?
# grep rootdev /etc/system
* rootdev: Set the root device. This should be a fully
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
rootdev:/pseudo/md@0:0,0,blk
Remember if this is a mirrored drive, when you boot from CD you may need to mount both sides of the mirror and make changes on both sides- otherwise the replication may not goes as expected.
Actually, I have run into problems with the modifying one side of a mirror this way. In the past Sun tech support would recommend that I break the mirror and then rebuild it once the system is up and running. So in your case you may want to boot from CD, mount the 1st disk slice, edit /etc/vfstab AND /etc/system, boot into the OS and use the various meta commands to delete and rebuild the mirror- or at least maybe to drop and reattach the 2nd 1/2 of the mirror.

Root password problem in Solaris 10

Hi All,
Have anyone noticed this problem before?
I've set the password on Solaris for the root user as "rootroot123". However, I'm able to login with any password that starts with rootroot (i.e. rootroot*)...
My solaris version is:
SunOS mynode01 5.10 Generic_138888-03 sun4u sparc SUNW,Netra-240
Is there a bug report in Solaris regarding this or any way to solve it?
Thanx,
Mahmood

I think by default Solaris uses CRYPT_DEFAULT=__unix__ which limits you to 8 characters.
in order to have more than 8 usable characters in your passwd, then you must use "md5"
CRYPT_DEFAULT=md5
this is located in : /etc/security/policy.conf
I think you may want to change the password length in /etc/default/passwd
PASSLENGTH= (default=6) change it to something of your liking.
be sure to do a little more research on the exact steps, but this is what you are loking for. im just going by memory here.

[SOLVED] Need to change root password - current one doesn't work

Hey everybody,
Not sure where to put this, so I apologize if it's in the wrong forum.
I just installed Arch on my Dell netbook and all is well, except for issues with the root password. I am having a great deal of difficulty getting it to work. I know for a fact that I am typing it correctly. However, I did have trouble getting it set during the installation. When I try several times, I have gotten it to work, but I am getting tired of having to do that, and now I can't seem to get it to work at all. I have even tried a different keyboard, but with no luck.
Is there any way to change the root password short of a reinstall?
Thanks in advance for any help, but please keep in mind that I am relatively new to Linux and would greatly appreciate detailed instructions.
Jeff
Last edited by jlr1701 (2010-08-12 04:10:50)

Solved. Should anyone else have this issue, I solved it by entering this command:
sudo passwd root
I set a new password and it seems to work fine.
Didn't know if it was possible to change the root password that way, but glad it worked!

So my daughter set a password to lock her ipod and now she can't remember it. I tried to restore to factory settings but it still wants a password. I tried 0000 and that doesn't work. Any ideas what to do to?

So my daughter set a password to lock her ipod touch and now she can't remember it. I tried to restore to factory settings but it is still asking for a password. I tried 0000 and that didn't work Any ideas what to do?

From this Apple support document: iTunes: Specific update-and-restore error messages and advanced troubleshooting
This device is not eligible for the requested build: Also sometimes displayed as an "error 3194." If you receive this alert, update to the latest version of iTunes. Third-party security software or router security settings can also cause this issue. To resolve this, follow Troubleshooting security software issues.
Downgrading to a previous version of iOS is not supported. If you have installed software to perform unauthorized modifications to your iOS device, that software may have redirected connections to the update server (gs.apple.com) within the Hosts file. First you must uninstall the unauthorized modification software from the computer, then edit out the "gs.apple.com" redirect from the hosts file, and then restart the computer for the host file changes to take affect. For steps to edit the Hosts file and allow iTunes to communicate with the update server, see iTunes: Troubleshooting iTunes Store on your computer, iPhone, iPad, or iPod—follow steps under the headingBlocked by configuration (Mac OS X / Windows) > Rebuild network information > The hosts file may also be blocking the iTunes Store. If you do not uninstall the unauthorized modification software prior to editing the hosts file, that software may automatically modify the hosts file again on restart. Also, using an older or modified .ipsw file can cause this issue. Try moving the current .ipsw file, or try restoring in a new user to ensure that iTunes downloads a new .ipsw.
Error 3194: Resolve error 3194 by updating to the latest version of iTunes. "This device is not eligible for the requested build" in the updater logs confirms this is the root of the issue. For more Error 3194 steps see: This device is not eligible for the requested build above.
B-rock

Root password not being saved

When I enable the root user it asks me for the password, then password verification. Then when I leave terminal I disable the root user. Next time I enable it, it again asks for the password and to verify it, but I can enter ANY password and get into SU in terminal. So anyone that can get to enable the root user and set a password. This is dumb or I am not understanding something here. The computer should remember the last password and use that password and not allow just ANY password to give super user access???
Rachael

I would be uncomfortable leaving the root user enabled. Frankly speaking the root password should be saved once I set it then disable the root user, saving that password for the next time I enable the root user it. Why is there even an option to change the password if it is not saved. Stupidity. Even setting the password in terminal with the passwd command will not save it. Stupidity. This is not how it worked in Snow Leopard. You set a password and it stuck. What is the point of having a password for root, it anyone can enter anything to reach it. Stupidity
But thanks for the suggestion
Rachael

I did re-set my password and when I click on Install for Mavericks, I still get a box for "administrator password" and it still won't accept my new password. Is there a difference between my Apple ID and the administrator password they're asking for?

I downloaded Mavericks and it won't install. I did re-set my password and when I click on Install for Mavericks, I still get a box for "administrator password" and it still won't accept my new password. Is there a difference between my Apple ID and the administrator password they're asking for? I never had an administrator password-- I just hit enter and have never had a problem before with previous installations. I'm on an iMac, from 2007, running Mt. Lion (version 10.8.5). I've been looking for other's posts who may be having the same problem, but haven't found any. Can anyone help?

Ugh. The 'no password, no work' thing is a recent Apple development. I ran into it on my system and ended up having to do a clean install on a partition I fully erased.
I suppose, if you have the ability to, go online and look up how to burn a bootable DVD image. Download the 10.8.4 image then use the Disk Utility to make a boot image of it. You'll need a dual-layer DVD or a USB drive (or memory stick at least 8GB) If you've got an optical drive, burn the disk, if you've a USB device, use that.
Then get a pocket drive and copy your important files off the system or let Time Machine do a full backup.
When the backup is done, insert the disk and hold down the C key until the machine boots off of the DVD. At the point you get to the start window, go to the menu and choose the Disk Utility.
In the Disk Utility, reformat the drive. You go to the actual DRIVE (not the Macintosh HD, but the root above it that is the actual hard drive device)
I always do this and *partition* it into several volumes, the benefit being, you can store all of your music, documents and importans stuff on that secondary storage volume you make - it will have it's own index and then the first volume is where you put the OS and it will have it's own index as well. That way, if the OS throws a wobbler and you need to reinstall, you don't lose your data.
Depending on the size of your hard drive, it is good to give your OS partition at least 60GB and optimally 100GB, and the rest for storage.
Name your volumes, use the little box sliders to manually size them or put that number in the size window, select for the format, Mac OS Extended (Journaled) and hit Apply and then the Disk Utility will quickly create your new partitions.
Once finished, quit the Utility and it will return you to the OS installer. Select the volume you want to install to and it should start up and install.
Once the installation is done, you'll get the new machine startup then you MUST put in a password for the computer. Once you're in, and to the desktop, don't bother with any Mountain Lion updates, go right to the App Store and get the Mavericks update and let it install the app to your Applicaitons folder, then do that install.
On a side note, there MAY be a way to make a disk image from the Mavericks application and avoid the entire Mountain Lion step.. I honestly do not know, but a bit of hitting the search engines may find out if there is. I think that if you looked for "make Mavericks boot disk or boot image' you may find something.
Good luck!

Root password expired - not your typical case

Hello everyone,
I apologize for asking what is a very FAQ, but I am unable to find an appropriate answer anywhere on the interweb.
The facts of my unfortunate situation are:
1. I am a newbie in the SA world.
2. I am even more of a newbie in the Solaris world.
3. I am administering a Production Database system on Solaris 9.
4. Within the last couple days the root password expired.
5. When I attempt to login at the console as root, I receive the following message. "Roles can only be assumed by authorized users."
It seems to me that root ought to be authorized to login to the console.
I've read that I can boot from the CD to resolve this issue, but the system in question has the CD drive disabled. If only I could figure out how to login to the console as root, I'm sure that it would let me update the password, but I don't know how to work around the "Roles can only be assumed by authorized users" issue.
Please help!
Thanks in advance for your assistance. It is greatly appreciated.

Well, I've learned an awful lot in the process of trying to resolve this issue. I'm still not there, but I'm getting close.
I have done a ton of research on the net, and I am unable to find any specific detailed instructions on how to fix the root password expired issue. So, I figured I would paraphrase what I believe are the detailed steps to be taken. If you see an error in my logic, or my syntax please let me know, as I will be beginning this process soon.
So, we have RBAC or Role Based Access Control on the Solaris 9 box, and the root password has expired. This is a pretty annoying situation to be in, but it can be fixed easily enough.
First, we'll want to gracefully shutdown all the processes which are currently running on the system. This is accomplished by executing the following command which will put the system into single user mode:
init -1
Determine where your root file system (e.g. c1t0d0s0) is located by typing the following command (you'll want to make note of the result):
/etc/vfstab
Next, we need to access the EEPROM. Before doing this, you should do execute the following command to see if your EEPROM is password protected.
eeprom |grep security
Look for the line that reads "security-mode=" If security mode is set to "none" or "none-secure" you're golden, proceed with the next step. If security mode is set to "command" "command-secure" "fully" or "fully-secure" you want to make sure you have your EEPROM password, otherwise you'll be in worse shape than when you started.
Assuming that you either have the EEPROM password, OR the system is set to "security-mode=none" you can proceed to the EEPROM prompt by pressing the following key combination:
Stop + A
You should now have an OK> prompt. Insert the Solaris 9 Installation CD into the CDRom drive. At the prompt type the following command to boot from your CD rom:
boot cdrom -sw
Once the boot sequence is complete, execute the following command to mount your root filesystem.
mount /dev/dsk/<root filesystem device file> /mnt
Once you have mounted the root file system, you will need to change the /etc/user_attr file to allow console access by root. Open /etc/user_attr with your editor of choice. On the line beginning with root::::type=role; etc etc change the setting type=role to type=normal and save the user_attr file.
Enter the following command to go back to the OK prompt:
halt
Then enter boot -s to reboot your system. You should now be able to login to the console with root, which will allow you to update your password. Once you have done so, do an init -3 to bring the user back up to the standard mode of operation.
Thanks again Jeffery for your help in this matter. I hope to have this situation resolved soon, but I want to make sure that all my ducks are in a row before I start playing Russian Roulette with my server. Does the above walkthrough sound accurate? Is there anything that I have misuderstood or overlooked?

ARD to set root password

Similar Messages

Maybe you are looking for