On TechNet i found a new tool: Policy Analyzer
On TechNet i found a new tool: Policy Analyzer
You can use CCTK from DELL to perform BIOS configuration. First download the latest version of “Dell Command Configure” under “System Management” category from dell.com/support
Then install it and run the “Dell Command Configure Wizard”
Edit it selecting the required settings.
The export the config clicking the button “EXPORT CONFIG” to be able to modify it later if needed.
Clicking on button “EXPORT .EXE”, and executable file will be created. Running this exe on the target machines, your BIOS settings will be applied.
The exe is silent but create a log on the same folder where you run it.
To deploy it via PSEXEC, some options is required:
– Put the EXE file on a share reachable by clients
– Run PSEXEC with option -s
DELL deliver also a powershell module for managing BIOS setting.
If you have WMF5 you can download it directly from http://www.powershellgallery.com/
Check if you find it:
If yes, install it:
Once installed, import the module:
Check if the provider is there:
Then browse the BIOS settings:
Like example, to set “Numlock” attribute enabled:
Set-Item –Path .\POSTBehavior\Numlock Enabled
I created and scheduled a script for send email when the user password expiration is approaching.
We are on a international company, so this script have an option to specify a file where the mail body is written in the appropriate language and with the appropriate info.
Here the parameters of Send-PasswordNotify.ps1:
New-EventLog -LogName “Scripts” -Source Send-PasswordNotify
You can change the eventlog where send the info atn line 49. If you change the eventlog, remember also to enable it for this script with the command above. Example: New-EventLog -LogName “Application” -Source Send-PasswordNotify
On Send-PasswordNotify.ps1 at lines 43-51 you can fine the parameters that you can adjust, like days before the expiration, smtp server, etc.
Copy Send-PasswordNotify.ps1 and mailbox.txt on the same folder.
Sometime our helpdesk need to reset offline file cache on Windows because corrupted.
I created a batch script (I do not used powershell because somewhere winrm is not configured):
You can pass as parameter the hostname/ip address of computer where you need to reset the cache. Use “.” to specify that you want to reset cache on local computer.
You need admin rights and a reboot of remote computer is required after the cache reset.
I had the need to write a script that make some directories changes but at the exit came back to the current directory where I ran it.
The pushd command saves the current working directory so it can be returned to at any time, optionally changing to a new directory. The popd command returns to the path at the top of the directory stack.
In Windows PowerShell, pushd is a predefined command alias for the Push-Location cmdlet and popd is a predefined command alias for the Pop-Location cmdlet.
This directory stack is accessed by the command Get-Location -stack in Windows PowerShell.
pushd and popd is available also on windows command prompt (CMD) and Linux bash.
PS C:\> pushd .\Data\Working\ PS C:\Data\Working> Get-Location -Stack Path ---- C:\ PS C:\Data\Working> popd PS C:\>
I had this warning on a bad wan connected DC:
Log Name: DFS Replication
Date: 30/03/2016 02:27:44
Event ID: 6004
Task Category: None
The DFS Replication service detected a conflict between two or more nTDSConnection objects while polling for configuration information. The DFS Replication service resolved the conflict between CN=1a46e70a-b0f5-410f-afdd-7049b1685292,CN=NTDS Settings,CN=MyDC,CN=Servers,CN=MySite,CN=Sites,CN=Configuration,DC=Domain,DC=Local, CN=b1f0fddb-18cc-459a-9891-15458f6c9a06,CN=NTDS Settings,CN=MyDC,CN=Servers,CN=MySite,CN=Sites,CN=Configuration,DC=Domain,DC=Local, CN=b377e129-e214-4c52-bbe8-867686db3cb7,CN=NTDS Settings,CN=MyDC,CN=Servers,CN=MySite,CN=Sites,CN=Configuration,DC=Domain,DC=Local, CN=c037d3d8-16cb-4ede-bf82-c2c72c025ea5,CN=NTDS Settings,CN=MyDC,CN=Servers,CN=MySite,CN=Sites,CN=Configuration,DC=Domain,DC=Local, CN=82dff205-bc51-4f00-bf18-c47e96215608,CN=NTDS Settings,CN=MyDC,CN=Servers,CN=MySite,CN=Sites,CN=Configuration,DC=Domain,DC=Local by using CN=ee5b0d6a-d843-48e5-8d8c-b3164dfa4b1a,CN=NTDS Settings,CN=MyDC,CN=Servers,CN=MySite,CN=Sites,CN=Configuration,DC=Domain,DC=Local.
This error means that there are some connection objects conflicting. To solve it run ADSI Edit and connect to “Configuration” naming context
and delete the connection objects listed in the event where the conflict was detected, making sure to leave the object after “by using” in place because it’s the working connection.
Right click on connection object:
and delete it.
Repeat the process for any additional connection object on eventlog.
Excluding the graphical but manual interface, you can used DELPROF2 or GPO.
This batch delete users profile on PCs (PC01, PC02, PC03) older that 15 days
Note: DelProf2 is the equivalent of delprof tools but with support extended to the latest OS. Fortunately he have the same syntax.
Opening Group policy editor, go to:
Computer Configuration/Policy/Administrative Templates/System/User Profile
and enable the option “Delete user profiles older than a specified number of days on system restart” specifying the days.