An excellent article on SIP password security:
These updates are required for autodiscover to work properly, amongst other things. Microsoft requires about 3 page navigations before getting to the actual downloads so here are the direct links (for now).
This is actually down to Exchange’s Suggested Contacts, I think.
If you open up Contacts, choose the Exchange account, you can search and remove the offending contact there. the actual list of “Suggested Contacts” appeared empty to me, but searching overall did return the contact in question, and removing it has finally removed it from the autocomplete list in Apple Mail.
The mobile device syncs to the ACT! Connect Portal, but entries from ACT! Pro 2012 do not make it into the portal, and nothing from the portal makes it into ACT!.
It seemed to stop working around about the time of switchover to British Summer Time (clocks moved forward 1 hr in the UK).
To remedy (after much messing about!), I first stopped the ACT Connect service (from right-click of the sync app in system tray), and then exited the sync/connect app from the same right click menu, and went into c:\documents and settings\all users \application data\act\mobility, and moved all the files there into a directory called old (basically I deleted them, but backed up just in case).
Upon restarting the ACT! Connect program, a new sync began, and everything has made it into the portal. We’re about to test portal -> program sync, but I’m sure it’ll be OK.
On Vista/7/8, the directory would probably be C:\ProgramData\Act\mobility – basically it’s the “All Users” profile appdata.
I should add that I did a “recover” from the sync applications right-click menu first. This clears out everything in the portal. It might not have been necessary, or maybe you’ll get duplicate data if you don’t do it?
Changed ESXi virtual machine from UEFI to BIOS mode, so that bios440.rom trick can be used for SLIC.
Instructions copied from http://www.firewing1.com/node/610#gpttombr
The actual GPT to MBR conversion
Through the Rod Smith’s guidance and a few dirty tricks, I was successfully able to convert my GPT partition – without data loss or deleting any partitions – and then boot Windows 7 in legacy/MBR mode. In order to do this you’ll need your Windows installation media at hand as well as a copy of the Fedora 16 Live media. If you don’t have a copy of Fedora 16 Live handy, you can download the Live media ISO (64-bit) from a local mirror here
- Boot your Fedora 16 Live media and wait for your session to start. If you’re having troubles booting, press Tab at the boot loader screen and try booting with the
- Depending on your graphics card, you’ll either be presented with the new Gnome 3 Shell or with the traditional interface. Start a terminal session by putting your mouse in the top right corner of the screen and typing “terminal” in the search (Gnome Shell) or by selecting Applications > System Tools > Terminal (traditional interface)
- Install gdisk:
yum -y install gdisk
This may take a few moments.
- Make a backup of your current GPT scheme:
gdisk -b sda-preconvert.gpt /dev/sda
- Now we will attempt to convert your GPT disk layout to MS-DOS/MBR. Start gdisk:
You should be prompted with:
Command (? for help):
rto start recovery/transformation.
gto convert GPT to MBR.
pto preview the converted MBR partition table.
- Make any modification necessary to the partition layout. See Rod Smith’s Converting to or from GPT
External Links icon
page for more details on this.
- When you’re happy with the MS-DOS/MBR layout, press
wto write changes to the disk.
- Shutdown Fedora 16 and boot from the Windows 7 installation media
- Enter your language & keyboard layout and then select the option to repair your computer in the bottom left corner.
- From the available options, select Startup Repair. Windows will ask for a reboot.
- Follow the previous three steps again to boot the Windows 7 installation and run startup repair
- Once again, boot the Windows 7 installation media but this time opt to open a command prompt instead of choosing startup repair. Type:
- Close the command prompt and run Startup Repair one last time.
That’s it! You should now have a bootable installation of Windows 7 on a MBR partition layout.
Windows 8: Newly installed (and working) printer missing from Devices and Printers, despite reboots.
Not only do newly installed printers usually take an age to appear in Devices & Printers on Windows 8, but they sometimes do not show up at all.
You can print from your applications, and the queue shows up under Print Queues in Device Manager, but no amount of restarting the print spooler, or hitting F5 within Devices & Printers, will help the new printer to show up where it should.
All that is needed is a reboot of the computer – however, Windows 8’s Hybrid boot feature, which results in rapid startups and reboots, is actually a hibernate as far as kernel and device drivers are concerned, and so a restart or shutdown in the normal sense does not fix the problem.
In order to perform an actual reboot of the operating system, go to an administrative command prompt (ctrl+shift while clicking on command prompt) (save your work first please!) and type “shutdown /r /t /0″ followed by enter.
If you’re as lucky as I was, your new printer will finally show up in Devices and Printers when the operating system restarts.
Thanks for this annoying problem Microsoft!
I would hope that you’d be able to hold down shift, or alt, or something, while choosing Restart or Shutdown from settings on the charms bar to initiate a traditional shutdown or reboot, but I haven’t heard anything to suggest that this is possible.
I did a little more Googling, and somebody said that if you choose Restart from the Win-X menu (hold Windows/flag key that’s in-between ctrl and alt, then tap X while holding that key), then a full restart is actually performed. I haven’t tried this myself though.
Placing RC4 cipher to top of the list fixes the FTP-SSL file upload problem (“550 The supplied message is incomplete” response to uploads) with IIS7 & 7.5.
(same as one of the fixes in : http://blogs.msdn.com/b/kaushal/archive/2011/10/03/taming-the-beast-browser-exploit-against-ssl-tls.aspx Move “TLS_RSA_WITH_RC4_128_SHA” to the top of the priority list.)
Unfortunately the given method for doing this (Group Policy) is non workable due to the 1023 char limit in the group policy value field.
Use IIS Crypto to make the job easy peasy. Now FTP-SSL uploads work.
Due to spamming SEO companies, comments are no longer accepted on this blog.
See screenshot for an idea of why:
This is the dude behind Xataface.
I love people who create and give great open source software to the world.
Xataface looks to be exactly what I was searching for. Like DabbleDB but better, self-hosted, and still here. Thanks Steve!
Nightmare. I have come across this twice now, and really struggled to figure out what’s going on. In both cases it was apparent that the problem was specific to the particular user – i.e. another user on the same computer was fine.
I tried the offline setup, and even the enterprise MSI setup – still will not launch chrome.exe
Well, I figured it out. It’s caused by a user-mode rootkit. This particular user did not have local admin rights on his computer so I guess that’s the only sort of rootkit that could take hold.
The computer had a history of some virus infection, with ESET v4 half-blocking a zbot.aoo infection.
Running malwarebytes, gmer, eset v4, zbotkiller as Administrator didn’t achieve much.
Running zbotkiller.exe (kaspersky) as the affected user found something, and then again another time, but problem still persisted.
Running GMER as administrator turned up nothing. Running GMER as the user turned up something of interest (“telnet server” hidden service or something). Problem still persisted though.
In the end, because it’s a user-mode rootkit, I rebooted, logged on as a different user (local admin), and loaded the affected user’s NTUSER.DAT profile into regedit, then browsed to his Software->Microsoft->Windows->CurrentVersion->Run key and removed about three offending entries from there.
All seems OK now.