Wednesday, October 06, 2010

BlackBerry Torch Doesn't Reconcile Inbox - Syncing


BlackBerry Torch Syncing Problem with BES 4.1, Exchange 2007.
This was a new BlackBerry Torch 9800 series phone. The user had problems with reconciliation from the begining although it was not noticed right away.

His outlook inbox surely did not match the phones renerding of the inbox. Messages that had been removed in Outlook were still showing on the the BlackBerry Torch 9800 phone. Not part of the problem, but this user had ATT service. The BES (BlackBerry Enterprise Server) was version 4.1. There were about another 70 users on the BES server but none of them had this issue. What was done to resolve was firstly to change the number of messages tracked on the BES server and enabled HARD delete tracking.
Those options can be found by logging into the BES 4.1 server:
- Open BlackBerry Manager.
- In the explorer view, click server.
- On the server configuration tab, click edit Properties, then click Messaging.
- For the hard deletes reconciliation option, select True from the drop-down menu
- Restart the BlackBerry enterprise Server services ( I recommend restarting the services from the services control panel applet, not from the BES manager).
To change the number of messages tracked (the default messages tracked is 100)
In the performance section change the value of the Message State database Size to 1000. 1000 is the max.
I also resent the service book for the user, resent the IT policy, resent the peer to peer key.

Thursday, December 31, 2009

Supporting Technology with Technology.: Enable 24 bit color in RDP for XP or 2003 Server



Supporting Technology with Technology.: Enable 24 bit color in RDP for XP or 2003 Server

Connect with true color 24 bit rdp to XP or windows 2003 server. A pre-defined default color limit on XP or windows 2003 server limits the color depth of RDP connections made to the the systems to a 16 bit maximum. How to configure the "server side" of remote desktop to accept connections at 24-bit true color. Windows 7, Vista, and Server 2008 already allow higher that 24 bit color by default.

Tuesday, November 24, 2009

What happened to dsa.msc in windows 2008 server



The simple truth is that it's no longer part of the default installation of the server OS, sorry. There's a logical explanation of this for sure. The first that comes to mind is security. Anyone with access to a server can load up users and computers on any member server. This is usually no big deal but with identity theft always on the rise, this is a convenient way to get additional information about users.

With windows 2003 a member server made a nice convenient gateway to AD users and computers by simply executing dsa.msc from the command line or from the start run command. while working out issues on another server, a handy look-up and some times a useful tool to add a test account or to make a quick change to an existing account , was running dsa.msc. Although in environments that had Exchange servers, running this from a member server would not shoe email properties, it was still useful and often meant having to avoid another remote connection to a domain controller.

The image in this post shows the options that should be selected to add this functionality back into member server. The installation of the feature does not require a reboot and only takes several minutes - of course that's on a dual quad core server.
A positive about server support , in particular when the server is an HP or Dell PowerEdge server, is the technology developed and incorporated into server support that facilitates remote access and remote control of servers from the local LAN or through the Internet. The technology that permits this remote control of the console is HP iLO and from Dell it is Dell iDRAC. These two technologies have enabled support to remote control the server's console without having to even have an operating system installed. The technology permits support through the network and on the web.
 

Wednesday, April 22, 2009

OWA-problem-loging-in-reason=0


OWA users received the following message in their address bar and a blank browser page. OWA worked fine before this started occurring. OWA was using forms based login and the work around to allow users to login again was to change from forms based login to standard windows authentication logon. Although hey achieve the same purpose, the users had become used to the forms based login and it was admittedly a nicer interface to use. The users got in the browser address bar:
https://mail.[exserver].gr/owa/auth/logon.aspx?url=https://mail.[exserver].gr/owa/&reason=0

This message would come up for OWA users connecting to an Exchange 2007 server. The solution to this problem was to uninstall microsoft exchange 2007 SP1 update rollup pack 6. uninstalling update rollup 6 solved the problem for the OWA forms based logon but but by uninstalling the rollup, the transport server was removed.

That's right, the transport server role was on this same exchange server and it was completely removed, not disabled or set to automatic startup but removed. This was a tough situation but something had to be done as there was no email going in or out of the email server. One choice was to re-install the update rollup 6 but that may have brought me back to the same problem. I decided to remove update rollup 5.

See, the problem here originated when a in-house guy who does a lot of the desktop work and some server work had some trouble with a blackberry server and decided to install all kinds of updates to the exchange server. The updates were windows updates and they were exchange updates. After updating the heck out of the server the OWA forms based login had been broken. The suggestion was to remove windows updates that were applied and that could resolve the problem.

The problem sure enough was caused by updates being installed while the IIS service was not running. The windows updates were removed and re-installed as prescribed but that did not solve the problem. It was a while before I was able to address this OWA logon problem again and now the time had come. remembering manipulating the windows updates I decided with a little confirmation from forums that the next approach would be to remove exchange updates.

I saw that update rollup 3,4,5,6 were installed and of course started with removing update rollup 6 in effort to make the browser stop hanging with blank page when logging into OWA using HTTPS. At the end of the URL in the address bar was a clue for searching, /owa/&reason=0.

Removing 6 solved the OWA logon problem but removed the hub transport service from the exchange server. I then decided instead of re-installing rollup 6, to remove 5. After removing rollup 5, the hub transport service was back and several other exchange services that were removed with update rollup 6.