@scottalanmiller said in Replaced Drive in PE T410 Not adding to Virtual Disk:

Non-Dell drive could initiate this kind of issue, though.

In the end, that is what we found. Adding it to the hot spares then threw the drive into "failure" so the drive was not new since it detected foreign and the OMSA logs are being picky about it not being a certified drive. I was not involved until the swap, so I would have recommended a Dell drive anyway.

@jaredbusch said in Replaced Drive in PE T410 Not adding to Virtual Disk:

I've never had to do this. The drives have always started to rebuild.

I tired that, but there are two options, you have to select an old one and new one to replace and since I do not have that option, I cant use that option.

We had to replace a predictive failure drive in the a Dell PowerEdge T410. Replaced it with a new Drive but OMSA was not detecting it properly as the status said Failed in OMSA, but it was showing the correct data. Drive size, Firmware, etc..

They replaced the drive back to the old one and reboot and thought it was due to the new drive being a Non Dell branded firmware drive and rebooted and it came up as Foreign. Powered the server down again and put the new drive in. Drive came up as foreign this time too. In OMSA, we cleared the foreign config.

Now the drive just says "Spun Up" and "Online" and it is not doing an array rebuild. The array just says degraded. Luckily this is just the data VD for Backups, and the OS is fine, but at same time I dont want to loose the backups.

No Dell Warranty so I cant call support. How do I save ourselves and get the drive back added to the array??

I am Remote with no idrac, can only leverage omsa.

Long story short, the previous guy left no documentation. I did find his template file however. Now I just the EMC shell syntax.
We have public folder data to add.
For example I have 95 lines of this just for this one year in a CSV.
New-PublicFolder -Name 910002 -Path \Projects\1991
New-PublicFolder -Name 910007 -Path \Projects\1991
New-PublicFolder -Name 910008 -Path \Projects\1991
New-PublicFolder -Name 910009 -Path \Projects\1991
New-PublicFolder -Name 910010 -Path \Projects\1991
New-PublicFolder -Name 910011 -Path \Projects\1991
New-PublicFolder -Name 910012 -Path \Projects\1991
New-PublicFolder -Name 910013 -Path \Projects\1991
New-PublicFolder -Name 910014 -Path \Projects\1991

Looking at this, it doesn't show how I could use a CSV instead of manually typing it in.
https://technet.microsoft.com/en-us/library/bb691104(v=exchg.150).aspx

I have 8 years to add like this. So I know he did it, I just have no idea what syntax he used to have Exchange shell grab from the CSV.

sitting in my office chair shivering. Furnance will not heat nor will switching it over to Cool will it run. Called it in last night and hopeful someone can come out today.
#warranty
#soundslikeafuse

@dashrender said in Windows 10 idle lock timer; 15 minutes:

@nerdydad said in Windows 10 idle lock timer; 15 minutes:

I know you said they are trying to go serverless, but how about Salt or Ansible?

Good question - he could just as easily use Intune or an MDM solution (like SodiumSuite).

Intune cost extra.

@black3dynamite said in Windows 10 idle lock timer; 15 minutes:

New-ItemProperty `
-Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System" `
-Name "InactivityTimeoutSecs" `
-PropertyType "DWord" `
-Value "0"

Nope.

@dbeato said in Windows 10 idle lock timer; 15 minutes:

Not even this?

powercfg.exe /SETACVALUEINDEX SCHEME_CURRENT SUB_VIDEO VIDEOCONLOCK 300

or

Registry Hive: HKEY_LOCAL_MACHINE 
Registry Path: \Software\Microsoft\Windows\CurrentVersion\Policies\System\

Value Name: InactivityTimeoutSecs

Value Type: REG_DWORD
VALUE: 300

Nope and Nope.

Spiceworks is down.

I am purposely cross posting for coverage, more the merrier.
Backstory:

Moved users to Azure AD. Of course there is no GPO unless you want to pay to enable AD DS and run a VM in Azure. Goal for this customer is to be serverless so that is not an option.

All of the google I have done with "screen lockout timer" and various other searches come up with all the pictures changes, sleep of the password window showing at the console of windows. Nothing I have found says, this reg key turn to 15 to enable 15 minute timer of being idle and the screen locks.

All I need is simple 15 minute idle timer that will then lock the computer, something simple that has been done before, I just need the registry settings in Windows 10 that you can change the value to like 15 to accomplish this.

Surely someone has done this in a workgroup environment to since that is essentially what this is. We have an RMM tool that will allow remote registry changes.