It took me a little while to find the appropriate definitions. But yes, that is 
absolutely the case, and it is OK to make that change. 0x6707001f is, in fact, 
preferred.

                {0x6707001e, 0x5, L"PR_URL_NAME" },
                {0x6707001e, 0x4, L"PR_URL_NAME_A" },
                {0x6707001f, 0x3, L"PR_URL_NAME_W" },
                {0x6707001f, 0x2, L"PidTagUrlName" },
                {0x6707001f, 0x1, L"ptagURLName" },


From: [email protected] [mailto:[email protected]] On 
Behalf Of Steve Norton
Sent: Monday, March 3, 2014 7:58 AM
To: [email protected]
Subject: Re: [Exchange] RE: ExFolders Add Property Error

I was running a version from 2010. Downloading the latest version from the link 
below and adding the property produces the same result. 0x6707001E changes to 
0x6707001F. In researching around the web I found one page that stated the F 
signified Unicode. I'm not sure what the repercussions of this are or why it 
insists on changing to an F.
Thanks.
Steve

________________________________
From: "Michael B. Smith" <[email protected]<mailto:[email protected]>>
To: [email protected]<mailto:[email protected]>
Sent: Sunday, March 2, 2014 11:26:08 PM
Subject: [Exchange] RE: ExFolders Add Property Error

Are you certain that you are running the most recent version of ExFolders?

http://gallery.technet.microsoft.com/Exchange-2010-SP1-ExFolders-e6bfd405


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Steve Norton
Sent: Friday, February 28, 2014 1:36 PM
To: [email protected]<mailto:[email protected]>
Subject: [Exchange] ExFolders Add Property Error

Exchange 2010 SP2. Setting up a Public folder for forms and am following 
http://technet.microsoft.com/en-us/library/gg236889(v=exchg.141).aspx. When 
performing Add Property To View using ExFolders.exe, I type 0x6707001E, and 
then click OK the trailing E turns into an F so what I wind up with is 
0x6707001F. Any suggestions on correcting this would be welcome.
Thanks.
Steve

Reply via email to