Within PowerShell can't use something like Push-Location \\Server\Share\path or Set-Location \\Server\Share\path and then run the cipher command?

NVM. Decided to work randomly.

@NerdyDad

You can use Loopback Processing also.

https://blogs.technet.microsoft.com/askds/2013/02/08/circle-back-to-loopback/

@nerdydad - Yes, you do get a skimped down version of Azure AD with the O365 license. The prerequisites mention using Azure AD, but don't say which one, except where they say that the Premium version is optional for auto enrollment with intune. Although, they have several plans/tiers, including 2 premium tiers.

I ended up going with an upgraded script by truly using powershell.

I found the answer here -
https://stackoverflow.com/questions/936108/how-to-script-ftp-upload-and-download

Essentially this is the script:

$File = "D:\Dev\somefilename.zip"
$ftp = "ftp://username:[email protected]/pub/incoming/somefilename.zip"

"ftp url: $ftp"

$webclient = New-Object System.Net.WebClient
$uri = New-Object System.Uri($ftp)

"Uploading $File..."

$webclient.UploadFile($uri, $File)

@Mike-Davis said in Autoupdates Killed My Windows Server 2008 R2:

most of what I have been working on for the last week should have worked...

When dealing with computers, should work does not always equal does work, lol.

Only the other night for me and it was all on one project so I'm not sure what it was, yet.

The XX concurent users only comes into play if the licensed application offers such a thing. In the case of something like Office 2013, you'd definitely need 300 license...

But for Something like... Raiser's Edge, or a Student Information System... You'd only need to license for the expected number of concurrent users.

IE: Raiser's Edge can be installed on every computer on my campus... But only 15 of us can log in at one time.

We run E10.0.700.3 at the moment (1 Server 2012 VM that runs SQL 2012, 1 Server 2012 VM that runs the E10 appserver, and 1 Server 2012 VM that runs RemoteApp for the E10 client - all on the same ESXi host) and will likely move to E10.1 in the next few months. We actually found that at sites with low internet bandwidth, RemoteApp is a little slower than when the client is installed locally. One site running a T1 told us that, and we confirmed it to be the case. It may have had to do with the nice metro interface in E10. The sites with 35/5 coax or 10/10 fiber seem to run RemoteApp about the same as installing the client locally.

I actually heard someone say at Epicor Insights 2015 that Epicor 10 ran better when installed locally on client machines connecting over site-to-site VPN. We never really had to test that theory other than at the site with a T1 that I mention here.

How goes your project?

Good way to think of it. Clean install is a little extra work today in exchange for a "known" or nearly known environment. An in place upgrade means carrying risk with you, maybe a little, but some that might bite you later.

Or maybe the next IT guy, just leave the headaches for him ;)