There are times when I want to yell at my client’s to just bite the bullet and invest in their own mail server vs using POP mail through their ISP, their are so many tangible benefits but I would have to say that the breaking point for me is when ISP pop mail is used in conjunction with a MFP scan to email functionality.
I love the functionality of most MFP’s scan to email ability. Pop in your doc, hit scan, and when you get back to your desk there is an email sitting in your mailbox with a new crisp PDF file of your document. Lot’s of other people love this functionality too and yet drawing the correlation between “why I can’t scan 10 pages of diagrams” and “you have a pop email account through your ISP what restricts your outgoing mail size” seems not to register with many. What is so hard to understand here? This doesn’t function by magic, it’s an attachment in an email and governed by the same rules. Yet when I explain this I am constantly beset by blank stares. Sigh.
I have been recently troubleshooting an issue where users are randomly and occasionally getting errors when XP cannot load their local profiles. Now my first though was that it was a problem with roaming profile but I soon discovered that this client enviroment did not use roaming profiles. After some hunting I found this excellent article which describes the issue.
In essence what is occuring in this enviroment is that one of the app’s they use is not shutting down properly when the user logs off and so when they try to log back in the ntuser.dat file for the profile is still locked in use by their last login and it generates a temp profile for them.
An interesting problem that I had never seen before.
A little note on something I found working with BES. In this situation we had an existing BES server and added a second one to the enviroment with the intent to move users over. During this process of deleting and purging users of the old server and adding an account to the server I found that the status of the account on the new server auto generates the PIN and changes it’s own status to Running, though it doesn’t actually work and activations fail. I found I needed to wipe the handheld before adding the user to the new BES before I could make it work.
Take a look at this:
I am truly shocked, not because they found a new flaw in a microsoft product that is pretty much par for the course. I am shocked that there are still apparently people who use IE! With so many much better alternatives out there some people still continue to use Internet Explorer. Boggles the mind.
Here is a citrix article I used recently:
This specifies a reg hack which will allow administrators to administer tthe citrix client created printers. We also found that it resolved an issue where users were occasionally getting access right errors to their own printers.
In IT news, RIM is attempting a hostile takeover of Certicom. Certicom makes encryption software including those that are currently in use by Blackberries. Even though RIM posted unfavourable news lately they clearly feel that there would be some good ROI on this acquision. Reports indicate that they attempted to speak to Certicom about a friendly acquision but never receieved a response. The cost on this is as of so far 66 million USD.
So despite the absolutely stupid Vista commercials that Microsoft has been pumping out lately it looks like they are still charging full speed ahead on releasing Windows 7.
Hmmm Microsoft rushing through a product release, how can that go wrong? Once again MS misses the boat on the importance of release a quality product.
I encountered an problem in Watchguard System Manager with service watch. The connection’s graph works fine but the bandwith graph does not. Watchguard has confirmed this is a known issue to be resolved in a future release.
So I posted a couple days ago about a problem with Fortigate causing traffic to be dropped. Fortigate support has been entirely unhelpful on this suggesting that perhaps it was a DNS issue or a HTTP profile issue. They tell me this after I explan that when I tracert the IP address the packets drop. Maybe this makes sense to them but how can tracert (ICMP) by IP address be either a DNS or HTTP issue? So we are “resolving” the issue be replacing the Fortigate. Congrats Fortigate on your excellent business model of having unexplainable problems with your product and hiring idiot’s in your tech support. Mazel Tov!
So usually I am on here posting solutions but today I am going to post a problem because I am having trouble finding a solution.
Here is the situation, a network protected by a Fortigate 100A firewall, they can’t reach a website. A tracert to the website shows that the packets are being dropped by a router owned by the local telco. Here is the twist, when we bypass the Fortigate it works fine. Now local telco claims it isn’t there problem (it never is of course, it’s only there router dropping the traffic) and Fortigate claims it’s not there issue (why would it be except of course the issue only occurs when we use their product) and so I have accepted I wil get help from neither of these … uhm guys. So any suggestions are welcome here.