Thursday, July 22, 2010
Friday, July 16, 2010
DHCP will not authorize after a re-IP of the server
You must first unauthorize a DHCP server scope prior to re-IPing the server. If you do not then you will be unable to re-authorize the scope after the re-IP.
If you have already re-IPed the server without first authorizing the scope open DHCP from Admin Tools, right-click on "DHCP" and go to "Manage Authorized Servers." Find the old DHCP server name/IP and click on "Unauthorize."
Once you have removed the old DHCP server you can authorize the re-IPed server.
If you have already re-IPed the server without first authorizing the scope open DHCP from Admin Tools, right-click on "DHCP" and go to "Manage Authorized Servers." Find the old DHCP server name/IP and click on "Unauthorize."
Once you have removed the old DHCP server you can authorize the re-IPed server.
Thursday, June 24, 2010
Mac Fonts
It is a good idea to remove all the fonts from ~/Library/Fonts and /Library/Fonts but leave /System/Library/Fonts alone.
Create a "My Fonts" folder, dump your fonts in there and activate when necessary.
Here are two good overviews of how the OSes handle fonts:
Leopard: http://www.prepressure.com/fonts/basics/leopard_fonts
Snow Leopard: http://www.prepressure.com/fonts/basics/snow-leopard-fonts
Create a "My Fonts" folder, dump your fonts in there and activate when necessary.
Here are two good overviews of how the OSes handle fonts:
Leopard: http://www.prepressure.com/fonts/basics/leopard_fonts
Snow Leopard: http://www.prepressure.com/fonts/basics/snow-leopard-fonts
Wednesday, June 9, 2010
Mac users can not log into a bound machine continued. Network home folder problem
Bound 10.6 machines require that all users attempting to log in with AD credentials have either a correct path to an accessible home folder or have “force local home folder” ticked in Directory Utility.
Here are some things to try:
Look at the user’s account and see if they have home folders listed. If they do, make sure they are valid and remove them if they are not. You might simply want to remove them full stop- this has resolved problems like this in the past. Something else to keep in mind: Snow Leopard has horrible problems connecting to SMB shares so if a user has a SMB home folder defined in their AD account it could simply failing to connect and halting the login process.
Use the work-around found in this TS article from Apple: http://support.apple.com/kb/TS3346
To force a local home folder do this:
Directory Utility > Active Directory > Show Advanced Options
Place a checkmark in "Force local home on startup disk" and uncheck "use UNC path from AD" to force a local home and ignore what's in the directory.
Here are some things to try:
Look at the user’s account and see if they have home folders listed. If they do, make sure they are valid and remove them if they are not. You might simply want to remove them full stop- this has resolved problems like this in the past. Something else to keep in mind: Snow Leopard has horrible problems connecting to SMB shares so if a user has a SMB home folder defined in their AD account it could simply failing to connect and halting the login process.
Use the work-around found in this TS article from Apple: http://support.apple.com/kb/TS3346
To force a local home folder do this:
Directory Utility > Active Directory > Show Advanced Options
Place a checkmark in "Force local home on startup disk" and uncheck "use UNC path from AD" to force a local home and ignore what's in the directory.
Subscribe to:
Posts (Atom)