Command-Shift-3: Take a screenshot of the screen, and save it as a file on the desktop
Command-Shift-4: Select an area of the screen and save it as a file on the desktop
Command-Control-Shift-3: Take a screenshot of the screen and save it to the clipboard
Command-Control-Shift-4: Select an area of the screen and save it to the clipboard
Michael
sudo adduser <username> admin
Michael
Edit the following files:
sudo nano /etc/hosts
sudo nano /etc/hostname
Edit the interfaces file (make sure you have root privileges).
nano /etc/network/interfaces
auto eth0 iface eth0 inet static address 172.0.0.100 netmask 255.255.255.0 gateway 172.0.0.250
Then restart the networking service
/etc/init.d/networking restart
Edit /etc/sysconfig/network
You’ll want to first open up the Terminal and then run the following commands:
Mac OS X 10.5
dscacheutil -flushcache
Mac OS X 10.4
lookupd -flushcache
I had an issue where a very long power outage caused my backups to fail multiple times leaving me with about 60GB worth of transaction logs in Exchange 2007. It ended up chewing through all my disk space causing my data stores to dismount.
Since I couldn’t run a backup to auto purge them, I had to perform a manual flush. Here’s the script I used:
$temp = (eseutil /mk "D:\Exchange Logs\First Storage Group\E02.chk")[13]
$Bottom_Log_File = $temp.remove($temp.IndexOf(",")).remove(0,$temp.IndexOf("x")+1)
Get-ChildItem "D:\Exchange Logs\First Storage Group" | Where-Object { $_.Name.Length -eq 15 -AND $_.Name -like "E02*.log" -AND $_.Name.Substring(3+8-$Bottom_Log_File.length,$Bottom_Log_File.length) -lt $Bottom_Log_File } | foreach($_) {remove-item $_.fullname}
Couple Things
- Make sure you change the file paths to point to your log location on lines 1 and 3
- Change the prefix of the log files lines 1 and 3
How To Use
- Copy the code to Notepad making sure that there is no word wrapping for line 3
- Save the file on the Exchange server as “C:\script.ps1″
- Open Exchange Management Shell
- powershell -noexit “C:\script.ps1″
That should start purging the transaction logs and allow you to re-mount the datastores. Now go ahead and perform a full backup.
Michael
Recently I ran into an issue where a service couldn’t log into its IMAP account. I double checked all the settings and verified the account could log in through Thunderbird. My last resort to troubleshoot was to enable logging for the IMAP service in Exchange 2007.
To enable logging, you need to have access to your Exchange server and edit the following config file depending if you want to log POP or IMAP.
\Exchange Server\ClientAccess\PopImap folder
POP
Microsoft.Exchange.Pop3.exe.config
IMAP
Microsoft.Exchange.IMAP4.exe.config
Look for the ProtocolLog parameter and change the value from false (default) to true. Also, make note of the location of the log files specified in the LogFile parameter.
Now restart the Microsoft Exchange IMAP4 service for changes to take effect and navigate to the LogPath location to see the logs.
Don’t forget to set logging back to false when you’re done. 
Michael
Recently I was using dnsstuff.com to run a domain name check and noticed that the email greet was 220 *************** instead of the proper 220 mail.acme.com ESMTP. Apparently if you’re running a Cisco ASA/PIX firewall there is an issue with it mangling up SMTP commands. The fix was to remove the inspect ESMTP line in the firewall.
Take a look:
ciscoasa(config)# show run policy-map global_policy class inspection_default inspect dns migrated_dns_map_1 inspect ftp inspect h323 h225 inspect h323 ras inspect rsh inspect rtsp inspect esmtp inspect sqlnet inspect skinny inspect sunrpc inspect xdmcp inspect sip inspect netbios inspect tftp inspect pptp
To remove the inspect ESMTP:
ciscoasa(config)# policy-map global_policy ciscoasa(config-pmap)# class inspection_default ciscoasa(config-pmap-c)# no inspect esmtp
To confirm:
telnet mail.acme.com 25 220 mail.acme.com ESMTP
Much better and now I get a perfect grade on dnsstuff.com
Michael
Scheduled power outage. Come in early with my Starbucks ready to power on all my equipment — no problem. Everything is on but wait, why can’t I ping my servers? After running some tests…
HyperTerminal into my D-Link switch.
# sh ipif Interface Name : System IP Address : 10.10.2.255 (dhcp)
Huh? Why is it configured for dhcp?
# config ipif system ipaddress 10.10.1.205/16 # sh ipif Interface Name : System IP Address : 10.10.1.205 # save %COPY-I-FILECPY: Files Copy - source URL running-config destination URL flash://startup-config Copy succeeded # reboot
Reboot is finished, try and ssh 10.10.1.205 and no go! HyperTerm back into the switch
# sh ipif Interface Name : System IP Address : 10.10.2.255 (dhcp)
Wonderful, my settings aren’t getting saved into NV-RAM. FAIL.