Is it because the file originated from the Internet zone? Sent from my (new!) BlackBerry, which may make me an antiques dealer, but it's reliable as hell for email delivery :-)
-----Original Message----- From: "Heaton, Joseph@Wildlife" <[email protected]> Sender: [email protected]: Mon, 9 Dec 2013 17:46:41 To: '[email protected]'<[email protected]> Reply-to: [email protected] Subject: RE: [NTSysADM] Odd issue migrating files That is one of the avenues we're being pushed down, but if it's simply a command line script through Robocopy, from one server to another, why would IE be getting involved? Joe Heaton Enterprise Server Support Information Technology Operations Branch Data and Technology Division CA Department of Fish and Wildlife 1807 13th Street, Suite 201 Sacramento, CA 95811 Desk: (916) 323-1284 From: [email protected] [mailto:[email protected]] On Behalf Of Rankin, James R Sent: Monday, December 09, 2013 9:36 AM To: [email protected] Subject: Re: [NTSysADM] Odd issue migrating files Isn't that something to do with Internet security settings or such like? I could be completely wrong.... Sent from my (new!) BlackBerry, which may make me an antiques dealer, but it's reliable as hell for email delivery :-) ________________________________ From: "Heaton, Joseph@Wildlife" <[email protected]<mailto:[email protected]>> Sender: [email protected]<mailto:[email protected]> Date: Mon, 9 Dec 2013 17:32:57 +0000 To: NT System Admin Issues Discussion list<[email protected]<mailto:[email protected]>> ReplyTo: [email protected]<mailto:[email protected]> Subject: [NTSysADM] Odd issue migrating files Source server - 2008 R2 Destination server - 2012 R2 Used a Robocopy script to move the files from source to destination. We did this on another file server a couple of weeks ago, and everything went fine. This time, we have a large number of PDFs that are "blocked". This is the block where you have to go into the properties of the file on the server and choose Unblock. The script was the same between the two, so it's odd that this happened. I'm assuming there's some setting on the server to maybe tell it to not do this with PDFs? But I'm not sure, and not having any immediate luck with my google-fu. Any ideas how to tell it not to do this, and, is it possible to en masse un-do this for the files that are already blocked? Thanks, Joe Heaton Enterprise Server Support Information Technology Operations Branch Data and Technology Division CA Department of Fish and Wildlife 1807 13th Street, Suite 201 Sacramento, CA 95811 Desk: (916) 323-1284
