[hrbuckley]

Hmm. I must not be holding my tongue right. I think I will uninstall and try again. If that doesn't work, I will try again at home with a fresh machine.

The time stamp is right, I unzipped it on a Linux box and found the policy names in there so I'm at a loss as to what is wrong.

[Grimlin]

Has anyone else gotten this same error? I am unable to reproduce the error.

[ebj75]

I just made an effort to reproduce this error to make sure I didn't forget something I did.

I opened ITPolicy2.sql in windows notepad and and saved the file (I didn't make any changes). I tried to load the data and got the same error message.

[Grimlin]

Thanks for helping out with the testing ebj. I am at work at the moment, so I can't easily duplicate. You are Correct. Since the file contains binary data, opening it with a text editor and saving it will corrupt it. I also would assume that a non-binary FTP transfer would corrupt it as well. Only extract it from the zip file once you are at your final destination (The Unite box). That is why I uploaded it as a zip to begin with.

[christophthered]

Maybe I missed something here, but does the default ITPolicy installed by Unite disable bluetooth connectivity to the Desktop Manager? Or is it just a matter of bluetooth connectivity to Unite not working?

[hrbuckley]

OK, at home I did a complete fresh install of all the stuff following Grim's instructions. Downloaded the zip file to the Unite box (was doing that before, just had a look at it on the linux box to insure something wasn't messing with it in transit). Extracted it and kept my paws off. Same error.

Would it be possible to post the hex strings for the blobs, or send them as a private message? Sorry to be so needy, I'm not normally this helpless when it comes to this stuff.

[hrbuckley]

Any way, in my thrashing about to solve this I have come to some other conclusions that may assist others. Some of this may seem obvious, it does to me now that I think about it, but I'll post it in case it may help someone.

Grimlin, and anyone else, correct me if I'm wrong here, but from tinkering with BES Express I concluded that a BES has fewer IT Policies than handhelds. This is of course the rational way to do it. The BES UI modifies the IT Policy record, and the modified policy is pushed out to all units configured for that policy.

Unite seems to use one policy per handheld. Since it is only going to support 5 units, this is not onerous and it simplifies the UI. The issue is that if one creates a single instance of a Policy and links a user or users to it, then uses the Unite UI to alter some Device Management Services parameter Unite will alter that policy record, affecting all users linked to it. This makes sense from a BES point of view, but would not be as documented. Of course when one modifies the controlling database behind the back of the program, one can't really expect behavior to be as documented. Just something to be aware of. And you may want to keep a backup copy of your ITPolicy2 table, just in case.

Finally, even though I haven't been able to use your file Grimlin, I want to thank you for publishing all of this data. If nothing else, I can go back and dust off my BES Express and replicate your work. Sounds like fun!

Oops, gotta go, have a Vet appointment to keep.

[Grimlin]

Originally Posted by christophthered

Maybe I missed something here, but does the default ITPolicy installed by Unite disable bluetooth connectivity to the Desktop Manager? Or is it just a matter of bluetooth connectivity to Unite not working?

Unless I am mistaken, the default functionality of a blackberry is to not allow bluetooth connectivity. ...or at least a blackberry with any ITPolicy at all. Unite lays down an ITPolicy. This blocks Bluetooth connectivity and any other browsers other than the Unite Browser. This is done so that you can control the browser through Unite.

[Grimlin]

Originally Posted by hrbuckley

OK, at home I did a complete fresh install of all the stuff following Grim's instructions. Downloaded the zip file to the Unite box (was doing that before, just had a look at it on the linux box to insure something wasn't messing with it in transit). Extracted it and kept my paws off. Same error.

Would it be possible to post the hex strings for the blobs, or send them as a private message? Sorry to be so needy, I'm not normally this helpless when it comes to this stuff.

When I was initially toying with it, I made a vbscript that read the handheld blob out of the database and displayed it. I will see if I can find it. If not, I will recreate. It will be later tonight or tomorrow though.

[Grimlin]

Originally Posted by hrbuckley

...Unite seems to use one policy per handheld. Since it is only going to support 5 units, this is not onerous and it simplifies the UI. The issue is that if one creates a single instance of a Policy and links a user or users to it, then uses the Unite UI to alter some Device Management Services parameter Unite will alter that policy record, affecting all users linked to it...

Great observation. That is absolutely correct and I should have pointed this out to everyone earlier. The reason for the ITPolicy per user is because to enable and disable phone, browser, etc, the Unite server has to modify the ITPolicy for the device.

If we were to really make this user friendly, we would need to create 6 new identical policies and completely replace the ITPolicy2 table. My current instructions only append to it. Why 6? Default is the one that the Unite server uses as a template. Unite1 - 5 are assigned to users. I assume that if you remove a user and add a new one back, it does not reuse an old policy, it probably creates a new one (Unite6, etc) and orphans the old policy. It would do this by making a copy of default and calling it Unite6. Then assign the new user to Unite6.

[John Clark]

So, who is going to be the BB Unite! admins for all these "home users" who install Unite?

Seriously, this is neat stuff guys. Good work!

[hrbuckley]

Originally Posted by Grimlin

When I was initially toying with it, I made a vbscript that read the handheld blob out of the database and displayed it. I will see if I can find it. If not, I will recreate. It will be later tonight or tomorrow though.

If you can find it great, otherwise you should be able to get it out by doing a select SQL querry in SSMSE. I did that to copy the blob from the default policy to Unite1 which gave me back my Internet and browsers (without putting the default policy at risk by linking to it ):

SELECT * FROM Unite.dbo.ITPolicy2

then:

UPDATE Unite.dbo.ITPolicy2 SET HandheldBlob = <hex string from policy desired> WHERE Id = <Id number of policy to change>

You are correct about the orphan Unite<n> policies. At one particular excursion I deleted then added my blackberry, I ended up with Unite1 and Unite2 policies.

I also noticed that if you modify the blob in an active policy with the BB processes running it is pushed out almost immediately.

[Grimlin]

Wirelessly posted

Cool. Will play with it more tonight.

[Grimlin]

Wirelessly posted

I reread your post. Are you actually getting something back in ssmse? I just get blob. Not the hex value. That is why I used BCP to export. I can use the console queries to copy stuff, but not to export blobs. I have to use vbscript or bcp.

[hrbuckley]

Wirelessly posted

In ssmes I click on new SQL Querry, enter the select statment, right click, select execute.

Mobile now so that's from memory, but yes I see the HEX. When I just open the table I see <binary>.

[Grimlin]

Wirelessly posted

I was just opening the table, that was the problem. Will pull hex values for you when I get home.

[hrbuckley]

Wirelessly posted

Sweet! Thanks.

[Grimlin]

Here is my ITPolicy2 table (the parts that matter)

Unite Policies
Name 			- OtherEmail 	- OtherBrowser 	- HandheldBlob
Default			- Yes		- Yes		- 0x050744656661756C7401
Unite1 			- Yes		- No		- 0x0505556E6974650101010201011301001E19030100040101050101010E556E697465212042726F777365726503020100780301010101
Unite2 			- Yes		- No		- 0x0505556E6974650101010201011301001E19030100040101050101010E556E697465212042726F777365726503020100780301010101


My Additions
Tracking 		- Yes		- Yes		- 0x0508547261636B696E672803200100300302010101
Bluetooth 		- Yes		- Yes		- 0x0509426C7565746F6F746822060A0100090100280320010001
Bluetooth_Tracking 	- Yes		- Yes		- 0x0512426C7565746F6F74685F547261636B696E6722060A01000901002803200100300302010101

[Grimlin]

Will update top post later with instructions for not using BCP

[hrbuckley]

Updated my selected policy with your HEX for Tracking. Withing minutes the dialog informing me tracking was activated start location processing (or words to that efffect) Yes/No came up. There is also now a Location Tracking option on the GPS options page. SyncLBS eventually got a record with the UserConfigId of my BB. Location and Alt are 0 but that could be due to signal strength in the house.

I would say its a success! Thanks again.