You have probably noticed that the “New” category in the App store is..well.. not that new.
Pinchmedia has started aggregating info from the app store to compile it into RSS feeds.
http://www.pinchmedia.com/your-view-into-the-app-s… for all the info.
For the lazy ones (*cough* efficient *cough*):
Here is another post I had on my Wiki that I think is still useful.
Purpose of this article
A lot of people encounter problems using Entourage 2004 on Exchange 2007 system. Errors with little detail such as “error 170″ happen when trying to receive or send email.
Solution
A few things need to be checked on the OWA side of things and a special way to enter the URL in entourage.
How to do it
On your Exchange Outlook web access server:
Internet Information Services (IIS) Manager
Open the web site containing your owa application. At the same level as the owa application, you should have folders called Exchange and Exchweb. Those are used for legacy applications.
Fig1: Checking if the legacy OWA folders exist
If you do not have these folders, use this command, posted by Mike Willis on http://benskelton.blogs.com/ben_skeltons_blog/2007/01/entourage_and_e.html (It is a simple command but I saw it there first, hence the credits) :
New-OwaVirtualDirectory -name exchange -OWAVersion Exchange2003or2000 -VirtualDirectoryType mailboxes
Then go in the Web Service Extensions at the bottom left of the IIS manager. Right click WebDav in the list, and enable it. After all of this, you might want to reset or restart IIS.
Fig2: Enabling WebDav
Open Entourage. With a bit of luck, it will connect with your old settings. If not, go edit the Exchange Server field in your configuration, and set it like this:
https://exchange.server.blah/exchange/user@host.com
User@host being your default email address, not your local domain account, unless they are the same of course.
It should then connect properly. If not, feel free to post in the talk pages and I will try to help you out!
A lot of people running ESX 3.5 Update 2 have been experiencing a slight bug where you can’t start or restart VMs starting August 12th 2008. Well, that could be a problem.
Here’s a thread about the issue with some workarounds which involve messing with the host’s time. (Watch out not to sync your Domain controllers with the wrong time, or bye bye Kerberos!).
Also, today is patch Tuesday by Microsoft and I’m sure a lot of people will be installing critical security patches and rebooting Virtual Machines. That should be interesting…but hey, people will learn not to patch stuff too fast.
The real issue with this is that VMware, an enterprise solution, has built-in license management. How can companies not realize that schemes such as this always hurt the honest customer? The dishonest ones are probably running cracked versions that weren’t affected by this.
Sometimes, it might be impossible to clean up all old domain accounts at the same time. Maybe you’re using Windows 2000 mixed mode and don’t have the LastLogonTimestamp field handy, maybe your users use some applications that don’t update it properly…there can be many reasons.
However, if it is a huge environment where there are a lot of administrators, and you know that the deprovisioning process is not always followed, you should at least disable the old accounts that are members of Domain Admin.
I use oldcmp by Joeware, maker of the greatest AD tools on Earth.
Oldcmp was originally designed to disable old computer accounts, but it’s also made to work with user accounts. It can use pwdLastSet and LastLogonTimestamp as attributes.
Check out the oldcmp usage first.
Then, it is a matter of running oldcmp with the proper switches, and filters. Always run it in reporting mode first.
oldcmp -users -report -af “memberof=CN=Domain Admins,CN=Users,DC=domain,DC=com” -llts -age 120 -format csv
oldcmp -users -report -af “memberof=CN=Administrators,CN=Builtin,DC=domain,DC=com” -llts -age 120 -format csv
This will output a CSV file with a list of Domain Admins that have not logged in for 120days+ according to the LastLogonTimestamp attribute. Of course, this attribute is not precise as it is replicated roughly every 2 weeks. However, this will give you a pretty good list of “old” admins.
Then, if you only want to remove them from the Domain Admins group, either do it manually or use admod to do it. If your domain is not totally insane, there should be few accounts to remove.
If you want to completely disable the accounts, you can use the same oldcmp string as above, with the safety and reporting removed. I’ll let you read the usage so you don’t blame me if you disable all your domain admins! If you are using pwdLastSet, watch out not to disable accounts that are set so that the password doesn’t expire..
You should do that on Enterprise Admins and other high privilege groups as well obviously, and also, on the whole domain.
Shamelessly stolen mp3 from http://www.modemsite.com/56k/trouble3.asp
Took the Crank one for somewhere I can’t remember.
Converted to m4r for iPhone goodness. Import to iTunes straight away and enjoy. Click on Ringtones tag for more!
