PDA

View Full Version : Direct Push registry settings?


GliTCH82
10-05-2006, 11:37 PM
I'm trying to see if there's some kind of registry setting that would allow Direct Push to use an available WiFi connection as opposed to forcing a GPRS connection. While searching for relevant keys, I came across these:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\ActiveSync]
"LastUIState"=dword:00000000
"KeepAlive"=dword:00000001
"MIMETruncation"=dword:0003E800
"MailBodyTruncation"=dword:FFFFFFFF
"DeviceID"="F0393738D4933383B0EF2423F0667416"
"SyncAPN"=""
"SendMailItemsImmediately"=dword:00000001
"PeakStartTime"=dword:000001E0
"PeakEndTime"=dword:00000438
"OutboundMailDelay"=dword:00000005
"MinHeartbeat"=dword:000001E0
"MaxHeartbeat"=dword:00000690
"HeartbeatIncrement"=dword:0000012C
"InitialHeartbeat"=dword:000001E0
"EnableNonLocalCrossPollination"=dword:00000000
"Device"="PPC"
"TcpPingRetryStepMs"=dword:000009C4
"TcpPingTcpRetries"=dword:00000005
"TcpPingDnsRetries"=dword:00000001
"Interval"=dword:00000000
"Retries"=dword:00000001
"Resilience"=dword:00000002
"NotifySyncDelay"=dword:00000000
"DisconnectWhenDone"=dword:00000001
"SyncWhenRoaming"=dword:00000000
"MailFileAttachments"=dword:00000000
"SaveSentItems"=dword:00000001
"BodyTruncation"=dword:00001400
"CalendarAgeFilter"=dword:00000004
"EmailAgeFilter"=dword:00000002


[HKEY_CURRENT_USER\Software\Microsoft\ActiveSync\Pa rtners]


[HKEY_CURRENT_USER\Software\Microsoft\ActiveSync\Pa rtners\{0DFDB9E1-74E0-5744-15C0-1CD660E700DF}]
"RetryCount"=dword:00000000
"RetryInterval"=dword:00000000
"LastSyncSuccess"=hex:80,73,DE,05,78,74,C6,01
"LastSyncAttempt"=hex:80,73,DE,05,78,74,C6,01
"LastSyncResult"=dword:00000000
"ErrorSeverity"=dword:00000000
"LastPingResult"=dword:06000701
"ServerNameChanged"=dword:00000000
"URI"=""
"EnrollForCertOnNextCradle"=dword:00000000
"DeviceSMSAddress"=""
"DeviceAddressingMethod"=dword:00000000
"CarrierConnector"=""
"Server"="mobile.exchange.mail2web.com"
"ClientRenegotiated"=dword:00000000
"EmailAddress"=""
"IsSecureIdServer"=dword:00000000
"TasksFolderId"="1b5349336f74fd48be3b785536ff9688-1d7f0ab"
"ContactsFolderId"="1b5349336f74fd48be3b785536ff9688-1d7f0a7"
"CalendarFolderId"="1b5349336f74fd48be3b785536ff9688-1d7f0a6"
"AutdSupportLevel"=dword:00000003
"PartnerIndex"=dword:00000001
"ClientProtocolVersion"="2.5"
"ClientNegotiated"=dword:00000001
"TempAirsyncVersion"="2.5"
"CommandsSupported"="Sync,SendMail,SmartForward,SmartReply,GetAttachmen t,GetHierarchy,CreateCollection,DeleteCollection,M oveCollection,FolderSync,
FolderCreate,FolderDelete,FolderUpdate,MoveItems,G etItemEstimate,MeetingResponse,ResolveRecipients,V alidateCert,Provision,Search,Notify,Ping"
"MSAS-ProtocolVersions"="1.0,2.0,2.1,2.5"
"ClientAuthCertRequired"=dword:00000000
"Logging"=dword:00000000
"ConflictResolution"=dword:00000001
"Domain"="ad2"
"User"= <Exchange User Name Here>
"SavePassword"=dword:00000001
"UseSSL"=dword:00000001
"StoreType"=dword:00000003
"Engine"="{22C7DA12-F3FD-4875-8344-7786454F6534}"
"Name"="Exchange Server"


[HKEY_CURRENT_USER\Software\Microsoft\ActiveSync\Pa rtners\{0DFDB9E1-74E0-5744-15C0-1CD660E700DF}\{783AE4F6-4C12-4423-8270-66361260D4F1}]
"Enabled"=dword:00000001


[HKEY_CURRENT_USER\Software\Microsoft\ActiveSync\Pa rtners\{0DFDB9E1-74E0-5744-15C0-1CD660E700DF}\{C6D47067-6E92-480E-B0FC-4BA82182FAC7}]
"Enabled"=dword:00000001


[HKEY_CURRENT_USER\Software\Microsoft\ActiveSync\Pa rtners\{0DFDB9E1-74E0-5744-15C0-1CD660E700DF}\{4A5D9FE0-F139-4A63-A5A4-4F31CEEA02AD}]
"Enabled"=dword:00000001


[HKEY_CURRENT_USER\Software\Microsoft\ActiveSync\Pa rtners\{0DFDB9E1-74E0-5744-15C0-1CD660E700DF}\{0DD8685C-E272-4FCB-9ECF-2EAD7EA2497B}]
"Enabled"=dword:00000001


Assuming Microsoft was kind enough to include a registry setting to allow this (maybe they did it during testing), what names and values do you guys think could hold relevance to what we're looking for?

mobileadam
11-05-2006, 12:33 AM
I spotted some of these keys when digging around. When I first implemented direct push I found that it has transmitting some traffic every 8 mins (there was also a problem with our ISA server dropping the https connection after 2 mins but that is another story).

Any I have changed one of those settings and from 8 mins to about 28 and the traffic count has dropped. Although I did hear that the settings are automatically updated as the system is used.

I find I need to turn off direct push if I want to use wi-fi which is a pain .

fergusstrachan
11-05-2006, 12:36 AM
I suspect the ISA server drops the connection every 2mins because that is the default timeout value on the web listener. :-)

Change that to 30mins (18000ms) as per the KB article (can't be arsed looking up the number). :-)

GliTCH82
11-05-2006, 12:43 AM
I find I need to turn off direct push if I want to use wi-fi which is a pain .

I wholeheartedly agree. To quote what I said in another thread:

This is not an issue of whether Direct Push should work over WiFi, this is an issue of not being able to use the device at all when WiFi is enabled while Direct Push is enabled.

If Direct Push wants to use a GPRS connection, fine, I don't mind. But I should be able to enable WiFi as well with no consequences, and Direct Push can still use the GPRS connection while the WiFi radio is on.

I have successfully tested this and it works. I was able to send my device an e-mail and have it notify me while WiFi is on, and when I browse the internet it uses the WiFi connection, not the GPRS one. But after a while of having both connections enabled, through some kind of bug or glitch the device will slow down till it eventually comes to a screeching halt.

There is no way that this is like this by design. If you can't enable WiFi with Direct Push enabled, then the system should force you to disable Direct Push before enabling WiFi or vice versa. But I believe it's a bug because even the WiFi icon has the ActiveSync animated connection graphic when both connections are enabled, which leads me to believe that Microsoft had anticipated a WiFi connection being active while Direct Push is doing its business over GPRS.