But where's the 25 Mbps service you promised us, TelstraClear?
Server ActiveSync users (Windows Mobile and other platforms such Symbian) will have lots of new stuff they can control from the server side:
New Policies – We've added a ton of new policies. Look for an upcoming post for details.
Bandwidth reductions – Less round trips and less data transferred while maintaining functionality.
S/MIME support – S/MIME has been added and has backward support for WM 5 + MSFP. We have not only added S/MIME but there is now policy control around the use of S/MIME.
Sync State Upgrade for Migrations – Allows users to maintain their setting while their mailbox is transitioned from Exchange 2K3 to Exchange 2K7 (no need to re-sync to the new server).
Default Policy Support – A default policy can now be set so administrators don't have to apply the policy to each user or write a script to iterate though users.
Cancel Remote Wipe – Canceling remote device memory/storage wipes is now available in OWA and though Exchange Management Console.
However, I see an update for Windows Mobile 6 in the horizon already, seeing that this very important line is there: "For the record, there is corresponding client work that needs to be done to fully deliver this functionality to end user."
We all know what it means: partners will get to the market first. Palm has added ActiveSync support to VersaMail, DataViz has incorporated ActiveSync into its RoadSync product for Symbian S60, Symbian UIQ, and Windows Mobile 2003 Second Edition. Nokia has also licensed ActiveSync for its Symbian S60 products and a few other partners are delivering products based on the ActiveSync protocol (even laptops with Windows SideShow, such as the Toshiba R400).
But updating Windows Mobile devices is always a pain, because we rely on mobile operator allowing the updates, which the way it goes requires people to buy new hardware a lot of the times (unless the device was release fairly recently).
Let's see how it goes this time...
This movie was filmed by Neil Blomkamp here in Wellington, New Zealand and is the first installment on a trilogy used to promote the Halo 3 launch. The team at Weta Workshop helped creating all the props.
Some of the photos I received from the filming:
I know there are some in the market - New Zealand's own Navman (now owned by MiTAC) and a couple of other software solutions. It will be good to see what the world's largest personal in-car solution provider will bring to the country.
I won't be able to be there it though, because I will be heading to Sydney to attend the Symantec Vision 2007 (had booked that already).
New Zealand timezone changes for Windows Mobile 5.0
New Zealand timezone changes for Windows Mobile 6
(And yes, if you read closely, even Microsoft is not using the new names Windows Mobile 6 Preofessional and Windows Mobile 6 Standard, still using the old Pocket PC and Smartphone naming convention...
First Windows Vista Service Pack 1 will not be available until sometime in Q1 2008. A small beta group will be able to test this release soon.
Windows Vista SP1 will address specific reliability and performance issues, support new hardware and support several emerging standards. The company says however that organisations can benefit from the security, management and deployment benefits of Windows Vista today without waiting for Windows Vista SP1.
The plans are to deliver the first Service Pack for Windows Vista in Q1 of the 2008 calendar year, but a beta programme will collect customer feedback before setting a final date. The SP1 beta will be released to approximately 10-15,000 private beta testers in a few weeks.
For users in general that are interested in finding out more about this release, I suggest reading the Windows Vista SP1 Beta White Paper.
First I will be a bit critical: I think everyone at IBM New Zealand, from General Manager Katrina Trroughton down, were the target of a viral distribution of Shift Happens (author, video, wiki) because the buzzwords and questions you see throughout the video were repeated a lot of times, by different speakers, during the whole day.
The keynote The New Working Frontier - How Our Children Are Beating Us to It, by Cliff Dennett, was worth attending. He traced a parallel between gaming and collaboration, attention management, and planning. Food for thought and very well put, although I wonder how many of the middle managers attending would feel inclined to go back to their desks and suggest something as revolutionary as using computer-based games to train and retain staff and clients. But if you attended the session, please put some work into that. It all makes sense, I assure you!
I then spent some time visiting the exhibitions around the show floor, and noticed the main topics around were virtualisation and unified communication - this a theme already present in the IBM Forum 06.
I had contrasting experiences when poking around the virtualisation area. While talking to IBM partner VMWARE I asked if I would notice any difference in performance between VMWARE Server and Microsoft Virtual Server. The technical person was clear: you might not notice any difference in performance between those two tools. And this gave me an incentive to actually try their virtualisation software later to see it by myself.
He then pointed out that VMWARE ESX Server would be a completely different thing: you see, VMWARE ESX Server is installed in the bare metal, and requires no OS to run - unlike VMWARE Server (Windows, Linux) or Microsoft Virtual Server (Windows). So one less layer to worry about, which can actually speed things up. But wait for Microsoft Hypervisor technology to show up soon...
Now the "interesting": I walked to the Integral stand (flash-based site) to find out more about their vision of Utiliy Computing. It just happens that their computing on demand solution is the use of virtual environments on blade servers, providing customers with additional power if the need arises. Well, if I understood correctly what I was told, it's like "we can run as many virtual servers you need in our hosted solution and if your requirements grows we can order more blade servers". Which to me doesn't mean "instantaneous elastic and resilient computing" under certain conditions.
Note that this approach is a bit different to what some mainframe companies are doing, where extra computing power is delivered with every system and always available on demand, with clients paying for a set level of performance, and any excess automatically metered and then charged to the client's account. Note that IBM themselves also provide some "metered computing".
But what really surprised me was when I asked the consultant to tell me how their solution compared with Amazon EC2 (Amazon Elastic Compute Cloud) and Amazon S3 (Amazon Simple Storage Service) and he didn't know about these offerings - interesting because I dare say Amazon EC2 is the cream in terms of utility computing, while Amazon S3 is the top of storage virtualisation.
But, yes, I am planning to be at the IBM Forum 08 when it comes back to town.
You use a 3G wireless wide area network (WWAN) data card on a Windows Vista-based computer. The WWAN data card uses a connection that only receives data. However, you may find that the throughput is much less than the throughput of the same 3G WWAN data card when you use it on a Microsoft Windows XP-based computer.
This problem occurs because of the way that TCP receive window auto tuning is used in Windows Vista for connections that only receive data.
Windows Vista obtains a round-trip time (RTT) estimate at the time of connection setup and every time that a new segment of data that is transmitted. A connection that only receives data is limited to the single RTT sample that is obtained at the time of connection setup. Because the connection only receives data, the connection cannot "converge" to the actual RTT of the connection. For example, because the RTT data may fluctuate for various reasons, a "converge" operation is performed to estimate a meaningful RTT by using blending current and previous RTT data. However, if the connection cannot converge to the actual RTT of the connection, the bandwidth delay product (BDP) estimate that Vista obtains is also incorrect. Therefore, the connection's receive window is limited, and throughput of the connected transmission network is reduced.
I believe most users will actually purchase a turn-key solution, a box ready to go from some partners, such as HP (pictured) and others.
But then you read some "expert" blogger comments such as this, and you have to really start thinking where this comes from:
On August 27, 2007, Windows Home Server is supposed to be released, and I'm in no hurry at all to buy it. I think there is no purpose for it! Who is really going to spend money on buying a new computer and operating system, just so they can share their files with other people? Home Server is said to cost around $500!
Wow! $500 is cheaper than some NAS devices. And it's not only for sharing files with other people. It's for home LAN management and maintenance, automatic backup with mirroring, easy restore tools, media distribution and more.
But if you keep reading it's clear he doesn't know it:
Before you go bashing me, just remember – I have not tried Home Server, and not many people have!
What I just said could be completely wrong! Home Server could be a huge breakthrough in technology, for all I know! I just think it's too expensive and too limited to Windows XP and Vista.
So you have not tried it and issue an expert opinion anyway?