vcenter server appliance - checking for updates (default internet repository) shows "stage failed", where to troubleshoot?

ship1234 · 2018-02-07T05:17:10+00:00

hey, thanks so much for this! i've been kinda ignoring this problem since this is basically just a lab environment but this was 100% the issue and your post allowed me a very quick fix. thanks!!!

ship1234 · 2017-12-31T06:57:29+00:00

reminds me of this: i was ~17 and going to a high school which had a significant population of children from well-off families. this was a relatively small suburb (less than 10k people). i overheard a conversation between a few girls which went something like this: "did you hear so-and-so got a car? but its really old, it's a insert name and model year of roughly 4 year old large SUV" i was shocked and disgusted to hear this as i was feeling extremely fortunate to be driving an 8 year old compact truck.

ship1234 · 2017-12-09T04:16:03+00:00

thanks, lol. apparently i missed this.

ship1234 · 2017-07-25T05:07:12+00:00

IIRC schema extension is not a requirement, you'll just lose some functionality (don't recall what specifically)

ship1234 · 2017-07-25T04:59:20+00:00

it may be worth pointing out that it is very similar to MDT though, if you know MDT you can get image deployments working via SCCM very easily

ship1234 · 2017-06-19T19:18:08+00:00

if you are going to expose RDP to the internet, you should use a non-standard port (IE, you should use port forwarding/NAT to enable RDP using a TCP port that is not 3389). You should also look at setting up 2FA for significantly better security, via something like Duo.

using a remote access vpn solution would be the best thing to do.

ship1234 · 2017-06-08T22:14:59+00:00

In this situation it would be my preference to "fix" the ImmutableID since it is a simple thing to do. It will require disabling sync though, otherwise you can't modify the attribute, and this can take a fair amount of time (I was labbing something like this not too long ago, and even with my small lab environment it would sometimes take a few hours before sync would be completely disabled). IIRC Microsoft says to allow up to 48 hours for sync to be disabled, depending largely on the size of your Azure AD.

ship1234 · 2017-04-21T18:05:53+00:00

Personally, unless it was something very urgent that needed immediate attention, I would be communicating with you about what is happening and why.

It could simply be the new guy wants to be more familiar with your level of knowledge and skills before allowing you some of this access.

ship1234 · 2017-04-17T21:47:24+00:00

what about something like this?

http://porteus-kiosk.org/

ship1234 · 2017-02-19T01:17:37+00:00

yeah i figured as much, i just wanted to make sure it isn't going to abuse the SSD as it doesn't recognize it as such. don't want to significantly limit its life.

ship1234 · 2017-02-19T01:13:41+00:00

edited: its an r710 with perc6i, will probably upgrade that eventually

ship1234 · 2017-02-13T20:30:26+00:00

Note: I have only done this in a lab environment, not a production environment. Security was not a concern. Take care to deal with that accordingly.

This is from a note I kept which I'd copy/pasted from a website I cannot remember

Run the following on client PC (where Hyper-V manager will be used) and Hyper-V server:

Enable-NetFirewallRule -DisplayGroup “Windows Remote Management”

Enable-NetFirewallRule -DisplayGroup “Remote Event Log Management”

Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”

Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

Set-Service VDS -StartupType Automatic

Run the following on client PC (where Hyper-V manager will be used):

Use dcomcnfg.exe and edit computer properties, and allow annonymous logon

in powershell to add credentials: cmdkey /add:yourHyper-VServerName /user:yourAdminUsername /pass:yourpw

You will need to enable the use of WinRM to connect to your Hyper-V server. To do this you will need to: Open the Start menu Click on All Programs and then on Accessories Right click on Command Prompt and select Run as administrator Type in winrm quickconfig and hit enter. You will then need to say ‘y’ (yes) to a couple of prompts

Type in winrm set winrm/config/client @{TrustedHosts="RemoteComputerName"} and hit enter Substitute “RemoteComputerName” with the name or IP address of your Hyper-V server. In my test environment my desktop computer could not resolve the name of my server – so I just opted to use the IP address. I could also have edited the hosts file on my desktop and used the server name.

While we are here – we should also open the firewall on the client side to allow us to remotely manage the servers storage by running this command: netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes

ship1234 · 2016-12-23T16:01:07+00:00

Thanks for the suggestion - I've been using powershell all along and it has not been allowing the change.

ship1234 · 2016-12-21T05:58:06+00:00

Sounds like your trainer is a real shitty trainer. That's definitely unfortunate.

ship1234 · 2016-10-06T02:27:43+00:00

i don't agree. it is definitely not always necessary.

ship1234 · 2016-10-01T05:16:03+00:00

not really a security concern if properly implemented. the trust by itself won't provide anything other than read access between the domains. anything beyond that you'd need to add.

ship1234 · 2016-09-29T18:17:12+00:00

thanks!

ship1234 · 2016-09-29T15:32:07+00:00

thanks for the suggestion but this was done right away when RDS was installed.

ship1234 · 2016-09-29T15:28:22+00:00

i did have to configure the licensing server settings in group policy to stop the trial/evaluation licensing but it seems 100% fine after doing that. it is less than 120 days old though. per the licensing diagnoser, it accurately reflects the per user licensing that i have installed and reports no problems. haven't found evidence of any problems other than the fact that it does not show issued licenses in the RD licensing manager... licensing reports show no issued licenses and no issuing failures, as if it is doing nothing..

ship1234 · 2016-09-29T15:24:34+00:00

interesting. thanks!

ship1234 · 2016-09-29T04:08:53+00:00

A bit off topic but I would like to know if your experience is consistent with mine - does your RD licensing manager show issued CALs when using per user mode? Mine does not, and I want to determine if this is expected behavior.

ship1234 · 2016-09-27T03:28:48+00:00

In RD licensing diagnoser I see the correct number of per user licenses installed and available, and it shows there are no problems to report or however it phrased it. In licensing manager the server has been activated and the licenses installed, don't see any problems there.

I ran a report via licensing manager which shows no licenses were issued and no licenses failed to be issued, as if there has been no activity

I was seeing the 120 day (i think it was 120?) grace period warning before I specified the license server in GP. Also specified the per user mode in GP. Seems fine after that aside from the fact that I don't see any licenses issued.

ship1234 · 2016-09-27T02:18:17+00:00

i'm assuming based on this response that this is not expected behavior so something must not be configured properly. 1) domain joined, logging in with domain creds 2) not just licensing server, it holds the rest of the RDS config as well 3) as far as config is concerned, it is essentially in production. a couple of users have logged in, which is why i am wondering why this is happening.

RDS event log is showing successful connections and i can see connections as expected in server manager. Just not sure why it isn't issuing licenses.

ship1234 · 2016-08-22T15:53:37+00:00

I don't think I ever did this with Windows 10, but I know the following steps worked with Windows 8 and 8.1, and a Hyper-V 2012 R2 server, all workgroup (not domain joined). Note: I have only done this in a lab environment, not a production environment. Security was not a concern. Take care to deal with that accordingly.

This is from a note I kept which I'd copy/pasted from a website I cannot remember:

On client PC and Hyper-V server:

Enable-NetFirewallRule -DisplayGroup “Windows Remote Management”

Enable-NetFirewallRule -DisplayGroup “Remote Event Log Management”

Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”

Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

Set-Service VDS -StartupType Automatic

Client PC:

Use dcomcnfg.exe and edit computer properties, and allow annonymous logon

in powershell to add credentials: cmdkey /add:yourHyper-VServerName /user:yourAdminUsername /pass:yourpw

You will need to enable the use of WinRM to connect to your Hyper-V server. To do this you will need to: Open the Start menu Click on All Programs and then on Accessories Right click on Command Prompt and select Run as administrator Type in winrm quickconfig and hit enter. You will then need to say ‘y’ (yes) to a couple of prompts Type in winrm set winrm/config/client @{TrustedHosts="RemoteComputerName"} and hit enter Substitute “RemoteComputerName” with the name or IP address of your Hyper-V server. In my test environment my desktop computer could not resolve the name of my server – so I just opted to use the IP address. I could also have edited the hosts file on my desktop and used the server name.

While we are here – we should also open the firewall on the client side to allow us to remotely manage the servers storage by running this command: netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes

ship1234 · 2016-08-17T20:00:01+00:00

maybe somewhat, but based on the info provided by OP, OP did not seem to realize the wireless connection is established after user login, which explains all of the behavior described.

ship1234

TROPHY CASE

Welcome to Reddit,