Mac Mail using Exchange Connection to SmarterMail InteractiveWebs
To Set up your mac mail with and Exchange Connection using Mac Mail you will need to follow these instructions carefully.
To Set up your mac mail with and Exchange Connection using Mac Mail you will need to follow these instructions carefully.
Mac Pro 2013 computer users have experienced problems in some configurations since upgrading to Mavericks OS X 10.9.3. For most people, the issue related to the use of mini port to DVI external monitors.
The mac pro by design can only run two Miniport to DVI monitors, and any additional monitors need to be run on a converter that has additional power. Apple call this their Dual Link DVI adapter. Essentially this is the same thing, just with a powered USB port on it. If you were to try an run 3 mini port to DVI adapters, what you would find is that only two monitors plugged in would run. Effectively the last two plugged in in any combination would be the two that ran.
Apparently this is by design, and part of the way that the Mac Pro is set to provide a stable and powerful signal in the miniprot to DVI adapters. The additional power that is required is subsequently provided by the Dual Link (USB port).
With this update, only two monitors would work, were previously more would run fine. Many online communities were talking about this problems that is considered serious for IT professionals. Here at InteractiveWebs.com we identified the problem, and lodged a support ticket with Apple. We had some back and forth providing the photo’s of our configurations, and some software tools that they provided to give system feedback.
Today we received a final version of OS X 10.9.4, and to our joy it has restored the monitor problems that we experienced and things are back and firing as they should.
I have seen some people digging in for a sledging of Apple over this issue. Personally I am old enough to have experienced this type of serious issue with other more prevalent operating system. In those instances, the disconnect between manufacturer, OS developers and software developers meant that we sometimes never fixed display problems. I can remember one instance with a Matrox graphic card that we paid something like $1200 for, and never could get it working as designed due to operating system changes and software incompatibilities. We later found the same cards on sale for $50 after we had dropped $6 K into the cards.
It was problems like that that, and the fact that no matter who we told our problems to (MS, Matrox, or 3rd party software developers) that we could never get a fix. No one would own the problem. That is exactly the reason we changed to “Apple Fan Boys” and although we have spent 10 days with less than optimal Mac Pro systems, it still remains that we had a problem. Told Apple, and they fixed the darn thing in a timely manner. Well done I say!
Green files and folders on Windows 7 indicate they are encrypted.
Usually this is a function of a program that will make these files encrypted for a reason. Security is usually the reason. But…
An interesting little bug in the process of creating a .zip file on a mac and moving it over to a Windows computer.
When a .zip file is created according to standards for .zip files found here:
They specify that .zip archives include a tag informing about itself to the program trying to decompress the archive. This tag information is known as the “version made by” and as the name suggest, it would tag information about the program version of .zip and the files system in use.
0 - MS-DOS and OS/2 (FAT / VFAT / FAT32 file systems) 1 - Amiga 2 - OpenVMS 3 - UNIX 4 - VM/CMS 5 - Atari ST 6 - OS/2 H.P.F.S. 7 - Macintosh 8 - Z-System 9 - CP/M 10 - Windows NTFS 11 - MVS (OS/390 - Z/OS) 12 - VSE 13 - Acorn Risc 14 - VFAT 15 - alternate MVS 16 - BeOS 17 - Tandem 18 - OS/400 19 - OS/X (Darwin) 20 thru 255 - unused
When the Mac system encrypts the files, it marks them with the attribute of being UNIX based files. Correct considering the Mac operating system is based on UNIX.
The problem arises at the Windows end. Because Windows is created by the most arrogant computer company in the world, it does not recognise that a .zip file could have been created with a computer that is not running Windows. It fails to correctly see the flag as UNIX and marks the files as Encrypted.
If the files are left as encrypted, you may find that there are problems if the files are shred on a network drive etc. Taking ownership will not change this flag, and resetting permissions does nothing.
Removing the incorrect Encrypted Flag on a green file in Windows 7, or Windows Server is really easy. Right click the file or files (holding the shift key to select multiple folders and files) then Click: Properties / Advanced / Un-tick the Encrypted Option
That’s about it. All fixed.
Who uses WordPress for their Blog… Microsoft!
Bouncing around the place today putting some updates to the Microsoft News App for iPhone and iPad.
One of the big sites for information and news around Microsoft for Mac products is naturally their own website.
What we did find interesting was the blog site on this Microsoft web page:
Is actually running on WordPress.
Which makes perfect sense to us, as we run the http://www.interactivewebs.com website blog on WordPress too. It really is so good for blogs, that at this time there is nothing better around.
We like it so much that we are recommending it to all our clients as a supportive SEO / SEM tool to bring hits to their site. We have setup our on server environment specifically for blog sites (and can offer hosted WordPress sites).
Just like the fact that good old Microsoft has dumped using their “junk blogs” in favour of a WP site.
Today, like a kid in a candy store, I upgraded to the new Mac OSX Lion from the Mac App store.
It can’t go without noting that it has been a long time since I was excited about the prospect of a new release software download. Today gave me glimpses of the days long gone when Microsoft would release new and innovative software. Those days are “dust in the rear-view mirror”. True geek like I know… but hay! You are the one reading this!
Generally it went exceptionally well.
Again I rebooted but wised up to this download. Rather than say, install. I quit the auto detected download prompt. Then went to the “Software Update” and asked it to check for updates. This time the updated worked, along with an iTunes update. All good.
We noticed that the Mail application that was updated and previously linked with an Exchange connection to our Exchange server 2010 ended up with two accounts. Both with the same details and same settings, both of them as IMAP accounts, and not exchange accounts.
We deleted both accounts from Mail. Then added the exchange connected account again, and this worked. Holding the details as an Exchange account.
Not sure why this happened, but it did happen on 3 machines.
Over the weekend Microsoft published a knowledge base article that outlines some known issues with Office for Mac on OS X 10.7. Overall, if you have Office 2004 and rely on it, then do not upgrade to OS X Lion until you have an alternative Office version installed (2008 or preferably 2011). Office 2004 is PowerPC code, and as with Intuit’s Quicken 2007 and earlier versions, if you install Lion then you will not be able to launch Office 2004.
Luckily there are options, including the ability to upgrade, or even install Snow Leopard in an alternative partition so you can still use Rosetta, but these may require you to either purchase new software licenses or set up a relatively cumbersome dual-boot situation.
In addition to the lack of support for Office 2004, there are a few situations in which Office 2008 and 2011 applications may crash. In Excel, a crash may occur when moving spread sheets between workbooks. PowerPoint may also crash when you use Command-Tab in presentation viewer mode. The only other known crash situations involve Communicator (only in Office 2011), which may shut down when initiating calls or messages.
If you regularly use any of these options or application functions, then you might consider waiting to upgrade to Lion until they are fixed.
The other interesting observation is that the scrolling is not only reversed (which we don’t essentially mind) but that in a few applications the scrolling is so bad it is virtually unusable. Xcode is a great example.
When using the new revered scrolling to browse simple lists of code, the stop start nature of the scrolling is so bad that it is almost unusable. It feels like your fingers may not have enough pressure when in actual fact they do!
All in all the update was exceptional. I cannot help but think back to MS updates that totally killed my system so often that I would NEVER consider a Windows Update, but would always start fresh with a new install. (What a pain). Never gain! Apple, your careful eye to easy end user experience has mean that as an advanced Windows Server Administrator I have never needed to “look under the hood” at your OS. Thanks for that!
That being said, clearly there are some bugs. Some of like the scrolling in Xcode make me wonder if updating is really necessary until they patch things like this.
To watch the video browse to the Apple Events (Apple Special Event) Website and Watch the streaming video from the WWDC 2011 keynote.
We use and manage an SVN server dedicated to our xCode development, but mostly because we can, not because we need to. We have the servers, knowledge and experience to do this so we did.
I thought I would suggest another way to share code among multiple developers, and still keep thorough backups of all the things you need.
There are a few exceptions and we will list them first.
1. Technically SVN allows for two people to work on the same code at the same time, and for those changes to be mashed together. Sort of. However this is not really the case. SVN does such a lame job of mashing when compared to some TFS systems we have used for years, that we would advise strongly against thinking it will solve this problem.
For this reason, we treat SVN as a single user project for modifications, but that all users can update their local copy of the code any time, and test locally.
2. SVN encourages you to keep the server repository separate and Update or download a local version for working. “A working copy”, that you can then update back to the server when ready for check in. The process works well, and forces some dev discipline.
What you need:
Skype, DropBox, Time Capsule
1. Create a DropBox account and share access to this for your developers. If you all use the same account, you can probably do this for free.
Drop Box will cache a folder to the cloud, and share that back to all users with the same account. Great service that just works!
2. Skype lets you talk to your other developers. Not really necessary, but a lever of communication is needed to ensure that you are not on the same project at the same time. This is nothing new to SVN that suffers the same problem and requires the same communication.
3. Time Capsule – This is to perform backups that are easy to revert to any point in time. We suggest that each developer has their own Time Capsule
1. The more connected and syncing to drop box the better.
2. Don’t work on code that is marked as check out to others, but you can grab a copy from any time and look / play with it in your working directory. You can even copy from someone’s working directory to yours.
3. Don’t check in over others checked out projects.
4. Be disciplined about notes and image originals into the correct notes folder.
That’s is. You own automates SVN in the cloud.
Easy. When you find a problem, you can use your time capsule to go back to any point in time for any project for any user directly from your time capsule. Any other team member with a time capsule can do the same.
The benefits are huge.
1. It actually gives you more protection and backup and SVN.
2. You all automatically have the latest code shared via Drop Box.
3. It costs almost nothing.
4. You have total control.
5. It works well.
Today I was trying to achieve something that was simple in Windows 3.1. Searching a directory in Windows, and checking the content of files for the search term.
In this instance, I was searching something from the content of a Web Server directory that contained some resx files. These files are used in a DotNetNuke website to deliver language content to a module.
In every version of Windows up until the "Mac Version” (that is the version that makes you get a mac… i.e. Vista). the ability to search was easy.
Now, in Windows 2008 server, they have replicated the crap that they call search in Windows 7. So basically no one know how to resolve some strange results.
I search the net and found many solutions, but non worked for me.
This appears to be one solution: (but who knows)
That’s it! You will now be able to execute searches on the Windows server through Windows Search Services.
Because this is a web server, I really have no desire to turn on service that case the machine to run indexing all day long and possibly slow down my machine.
So I decided that after 30 minutes of rooting around like a novice on something as simple as this, I should stop wasting time and just do something I know.
I pulled down all the files to my local Windows 7 machine, and searched the files there. Low and behold, NOTHING. Apparently I did not give the machine enough time to index or something.
So I folder shared the files to my shiny Mac, and within a few seconds had the result that Microsoft failed to give me on two operating system, and to someone with years of server admin / network admin experience.
I find that as I get older, I just don’t have the time or inclination to jump through all the Microsoft hoops to get something like search to return a simple result.
Microsoft… you blow chunks!
I was asked the question today. How do I open some Microsoft Publisher files with the .pub extension on my shiny new Mac. The answer is that you cannot really do this unless you have a virtual windows machine running in your Mac.
This is something that a lot of people do after they convert over from Windows to Mac, because they feel lost without the BSD (Blue Screens of Death) and the constant security messages.
“Would you like to open the web page that you just asked to open”. “Would you like the web page that you just acknowledged that you want to open to open.” “Do you realise that content on the web is insecure and may harm your junk Windows machine?” “Would you like to remember these settings?” Well guess what, you can’t because you don’t have the permissions as the only user on the computer to change these settings!”
Anyway, most Mac users soon get used to the fact that you can do everything a Windows machine does, just a lot easier. So they soon blow away the virtual machine.
Unfortunately .pub files cannot be run natively on any Mac software. But there is a solution.
Point your Web browser to pdfonline.com/convert-pdf. This is an online resource that will convert many different file formats to PDFs.
Click "Choose File" and select the PUB file you would like to convert and view. Your operating system’s file manager open so you can find your file.
Type your output file name in the appropriate text box.
Type your email address in the appropriate text box. Make sure you are using an email client that allows for attached files.
Click "Convert to PDF" button located on the bottom of the screen. It should take only a few minutes for your file to arrive in your email inbox.
Open your email client and locate the email from Doc2PDF Online.
Download the file from your email client and open it with a PDF viewer. Your PUB file should be viewable as a PDF with all of the original file formatting.