ITGURU

has anyone been able to test this on 2012 R2 as to whether they are still prompted on Windows 7 clients the second time and requiring domain\username like i do?

I inherited a Dell R515 server which at one point was experiencing multiple drives with predictive failures, seems to have settled down now and luckily had 1 drive set as a hot spare. The one thing that annoys me is when Dell (or HP for our other servers) say have you ran the diagnostics tool etc etc in case it's a backplane issue, Well if it says the drive has failed, its failed. Dell told me as I had 3 fairly close drive failures they wanted to come out and replace the backplane. I told them no need, they are drive failures. Year and a half one it' all been fine with no failures.

From what I recall, Papercut picks up the shared printers on the server, so if you rename the printer and share PaperCut automatically picks up the changes?

Yes using 2012 r2 here - with the modifications it doesn't second prompt on windows 8.1 but on 7 it does.

After inserting the code and logging on for the main screen it removed the first character from the username, so comes up saying invalid login!

Sent you a PM.

I cannot get this to work for Windows 7 clients - I still get the second prompt after launching the app and requiring domain\username

Thanks, now working without need for entering the domain or credentials twice, or if prompted can enter without prefixing the domain! However, for the access i'm using a UCC certificate and the remoteAPP external URL is not the main certificate name, it is one of the SAN names so I receive the 2 certificate errors below as part of the access. Anyone know how to remove these prompts? thanks.

do you mean I change: bPrivateMode = objTSFormAuthTicketInfo.PrivateMode; TO bPrivateMode = TRUE ?

I have searched the file but no results for objTSFormAuthTicketInfo.PrivateMode

my default.aspx code seems to be different or the bprivatemode entry. TSFormAuthTicketInfo objTSFormAuthTicketInfo = new TSFormAuthTicketInfo(HttpContext.Current); strUserIdentity = objTSFormAuthTicketInfo.UserIdentity; bPrivateMode = objTSFormAuthTicketInfo.PrivateMode; strDomainUserName = objTSFormAuthTicketInfo.DomainUserName;

I am using WindowsServerBackup on a server to back it up to another server - all servers are on same IP Range/Subnet etc.. When I run the backup from the source it is intermittent as to whether it completes or not. Whether it's the scheduled backup time daily or I attempt the backup manually some days i get 2 SUCCESSFUL backups, other days it can fail on the scheduled run, fail again on second run, then complete on the third. The error message is failed ; network path is no longer available. Whilst the backup is running I have monitored the following: - Ping - both local and remote server can constantly ping each other with no timeouts from cmd prompt - I have installed monitoring software which shows 0 packet loss throughout the whole duration from start of backup to failure - I can access both the source and remote server at all times by UNC path, IP, and DNS Names. Therefore I don't know why it should be failing. Anyone had this, or able to advise?

Windows Server 201 R2- 3DC's all set to host the namespace. All Workstations are Windows 7 x64 I will try hosts file before re-imaging but as mentioned, if I ping the dfs root domain it responds with the DC IP...

Some users may be out of signal range, then when back in range they receive the message. Remember the days of new years eve when everyone sent texts and you got them hours later?!

I'm hoping that AZT3122048B is not your domain name otherwise this would imply that all Domain Users are local administrators on the PC!

I've had mapped drives working without issue for years using UNC paths to each server. I am now moving over to DFS,. There is 1 PC (that i have been made aware of) that refuses to connect to the DFS root and shares. I can still access shares by \\servername\ and by \\ipaddress of all domain controllers, and can see all the dfs root shares. If i ping the DFS name it responds. The error is below: I've tried static IPs, flushing the cache, re-adding the PC to the domain with no success. For now i've manually mapped the drives by UNC path, but plan to re-image the PC tomorrow unless anyone can shed light on a solution before this.

Iperf is good.

EasyThumbnails - can overwrite the originals or save compressed files to another folder.

Internally I don't get any additional prompts after clicking the APP - it goes straight through. It's only external I get all the prompts for username and password again.

I already have that in place.. except I had termsrv\server internal name FQDN I have added in the external URL but made no difference. Whe I get the second prompt it does say connecting to internal server FQDN.

Running the script has now changed the remote computer and gateway server to the correct names, but the Publisher one is still the main name on the certificate, not one of the SAN names.. ..

On the prompt, the gateway server address is correct, but the publisher address shows the UCC Certificate main name for the certificate. So is that the one I change using the powershell?

Is there a powershell command to check what the current URL is set as?

How does this work with UCC certificates? My RemoteAPP url is one of the additional Subject Alternate names so we always get the prompt for certificate mismatch but still lets us continue if allow it.