My latest Inc Post, 6 Things Every Boss Must Do to Help Employees Stay Calm Amidst Change, is up at
It starts off like this:
I once spent hundreds of hours creating a training program and corresponding curriculum.
It turned into a lesson on how quickly things change in the technology industry — the program was out of date within two years.
The experience also was frustrating in another way. We had too many rules at the company about how things were created, so changing the program was a tougher bureaucratic slog than it should have been.
krypted August 3rd, 2017
Posted In: Business
Business, change, Change Management
Any time doing a migration of data from one IP to another where that data has a DNS record that points users towards the data, we need to keep the amount of time it takes to repoint the record to a minimum. To see the TTL of a given record, let’s run dig using +trace, +nocmd to turn off showing the version and query options, +noall to turn off display flags, +answer to still show the answer section of my reponse and most importantly for these purposes +ttlid to toggle showing the TTL on. Here, we’ll use these to lookup the TTL for the www.krypted.com A record:
dig +trace +nocmd +noall +answer +ttlid a www.krypted.com
The output follows the CNAME (as many a www record happen to be) to the A record and shows the TTL value (3600) for each:
www.krypted.com. 3600 IN CNAME krypted.com.
krypted.com. 3600 IN A 18.104.22.168
We can also lookup the MX using the same structure, just swapping out the a for an MX and the FQDN with just the domain name itself:
dig +trace +nocmd +noall +answer +ttlid mx krypted.com
The response is a similar output where
krypted.com. 3600 IN MX 0 smtp.secureserver.net.
krypted.com. 3600 IN MX 10 mailstore1.secureserver.net.
krypted January 23rd, 2014
Posted In: Active Directory, cloud, Consulting, iPhone, Kerio, Mac OS X, Mac OS X Server, Mac Security, Mass Deployment, Microsoft Exchange Server, Network Infrastructure, Windows Server
change, code, dig, DNS, Linux, MAC, migration dns, named, trace, ttlid, windows
DeployStudio has a very nice background image that it uses by default for the NetBoot set. But you can customize the image that’s used if you wish to have something more, well, customized. Simply mount the DeployStudioRuntime sparseimage file from the DeployStudioRuntime nbi file that was created when you elected to generate the NetBoot set. You can do so by simply opening the nib file and then double-clicking on the sparse image. From here, browse into the System and then the Library and then the CoreServices directory in the NetBoot set. From here find the DefaultDesktop.jpg file. Replacing that file will replace the background that is used when you boot to the NetBoot set. The higher resolution the better!
krypted November 17th, 2009
Posted In: Mac OS X, Mac OS X Server, Mass Deployment
background, change, DeployStudio