we enabled double escape to deal with + characters. might work on others. On Fri, Aug 2, 2013 at 10:05 AM, Al Corsi <[email protected]> wrote:
> Thanks for the feedback, renaming is basically how we're resolving. > > Do you know of any native OS commands or third-party utilities to help > identify files with special characters? > > > Jason Sandys <[email protected]> wrote: > > That’s not a BITS or IIS issue, it’s a ConfigMgr issue when checking the > hash value of the downloaded files. Best course of action is to rename the > file if possible (and yell at the vendor for doing weird things like that). > You could always wrap your installation command in a batch file that > renames the file back if you need to.**** > > ** ** > > J**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Al Corsi > *Sent:* Friday, August 2, 2013 9:14 AM > *To:* [email protected] > *Subject:* [MDT-OSD] CM 2007 OSD TS fails with hash error with special > characters file names**** > > ** ** > > Hi there, occasionally we get a package with special characters > (registered trademark (R) for example) in the file names. During the BITS > download, the smsts.log reports "hash error", which we`ve narrowed down to > the special character in the filename.**** > > ** ** > > With the special character in the file name, OSD fails and abruptly exists > with a hash error. Rename the file and the OSD TS completes.**** > > ** ** > > Is there a way to configure IIS or BITS to not care about or simply allow > special characters in file names?**** > > ** ** > > Thank you, Al Corsi**** >
