[Maurits]

In addition to sonata1666, I use a custom volume name, and if I changed line 666 of the script (r.459) to this line:

TARGET_IMAGE_MOUNT=”$TARGET_IMAGE_MOUNT/$ASR_FILESYSTEM_NAME”

now it seems to work with my custom name to make a simple image.

Funny enough I have to specify the InstallESD file, otherwise it fails… This is the command I used:

sudo ./instadmg.bash -m 1082_SUA -n MLionHD -I InstallerFiles/InstallerDiscs/InstallESD.dmg

Have to test the image yet, but it looks OK.

[Maurits]

I would NOT assume that you can simply replace System.dmg inside, since I expect that some details about System.dmg will be stored elswhere.

Why would you mess with images this way?

In System Image Utility (SIU) you can save a workflow, and run  it again with different settings.

If you have a dmg file that can be restored, mount it by double clicking, and use that mounted volume as a source for SIU netrestore set.

If you want more flexibility than SIU provides, I would recommend to look into DeployStudio. On their website is some good documentation how to set that up: http://www.deploystudio.com/Doc/Doc.html

 

 

• This reply was modified 11 years, 8 months ago by Maurits.

[Maurits]

in LDAP/…./PresetUsers

in 10.5 and 10.6 use Workgroup manager, set preferences to ‘show all records tab and inspector’ and select PresetUsers(or PresetGroups) from the pulldown menu.

In 10.7 use Directory Utiltity, click Directory Editor, and same path.

But I am not sure if it will help to edit the entries directly if the Workgroupmanager GUI failed (which I presume you tried)

[Maurits]

I am not sure, but it may be that the issue is not DCHP, but NFS and TFTP that is not getting to the clients

BSDP seems to work since you see the netboot server from the client in Startup Disk Preference pane.

In managed/routed/VLAN environments these protocols (UDP based) will not pass through routers.
If that is your issue you have two options:
1-convince the network admins to allow TFPT, NFS and BSDP across the routers/VLAN’s
2-try to serve the netboot image over HTTP and hope that TFTP does pass.

When you used the sudo bless command, did you specify the netboot server by ip address? that is the safest way.
Is there anything in the log of the netboot server? (to see how far the clients gets in the boot process)
read this for more information:

[url=http://www.bombich.com/software/nbas.html]Netboot acros subnets – how it works from and utility bombich.com [/url]
[url=http://www.bombich.com/mactips/bootpd.html]In depth analysis how netboot works with dhcp and BSDP from bombich.com [/url]

[Maurits]

If your LDAP server is a Mac OD server, this will work:
[code]ldapsearch -x -LLL -H ldap://host.domain.com -b “dc=host,dc=domain,dc=com” objectClass=apple-group memberUid apple-group-memberguid[/code]
The last one (apple-group-memberguid) is to make sure you get nested groups as well (the GUID’s in the example below refer to the users that are also listed in memberUid, if there is an adiitonal GUID, it will be a group) On the Mac server you can find this better with dsmemberutil (see man page). If you are using only ldapsearch you need to do it in two steps.
in my server this returns groups formatted like this:
[code]dn: cn=leominigroup,cn=groups,dc=host,dc=domain,dc=com
apple-group-memberguid: BB2792F2-1F75-43F7-90A8-69EB19937277
apple-group-memberguid: 95167831-E803-4E4F-A728-AF3039A5FF47
apple-group-memberguid: 30AAC8D1-E29A-479A-A60B-5E845345EE62
memberUid: arie
memberUid: ben
memberUid: caro[/code]
for all details: use
[code]ldapsearch -x -LLL -H ldap://host.domain.com -b “dc=host,dc=domain,dc=com” objectClass=apple-group[/code]
and see all group information.

[Maurits]

You can use advanced, or stick to standard plus add FTP using server admin.

The ‘secret’ trick is that for those items NOT in standard, you can use Server Admin and Workgroup Manager .
You will get a question if you want to upgrade to advanded, just click no, and continue.

This works fine but DON’T change any settings that is supposed to be managed by Server Preferences.

The advantage or standard mode, is that a lot of settings are set to default values, and if you use the ‘advanced’ tools, you have to specify everything yourself. The standard mode (at inital setup) works fine, AS LONG AS YOU HAVE DNS CONFIGURED FOR YOUR SERVER IP ADDRESS. (as always with Mac OS X Server) because standard will configure your system as OD master, while advanded will make standalone.

[Maurits]

I think of two things:
-the powerbook that does not ‘see’ the workgroup has SMB browsing turned off (with Directory Access utility)
-the computers are not synced with the list of workgroups (may take a few reboots, or a few hours)

On a small network, where all computers have the same workgroup name (default is WORKGROUP) the finder will not split up the file servers in the Network browsing, and show a list of computer names.

If there is one computer that has different name for its workgroup (or with appletalk zone) all computers should suddenly split up all file servers into My network, WORKGROUP (and any other workgroup name/appletalk zone), but that may take a while as noted above.

You can change the workgroup name of the mac in Directory Access (SMB options)

read this kbase for more information:[url] http://docs.info.apple.com/article.html?artnum=107804%5B/url%5D
maurits

[Maurits]

Have you tried?

when i use this code in a simple webpage it works (on a mac, in safari)

[code] maurits sharepoint[/code]

maurits

[Author]

Posts