Note: This procedure should not be performed on a local datastore on an ESX host where the operating system is located, as it may remove the Service Console privileged virtual machine which is located there.
Storage vMotion, move, or delete the virtual machines located on the datastore you would like to recreate with a different block size.
Log into the Local Tech Support Mode console of the ESX/ESXi host. For more information, see:
AdwCleaner is a program that searches for and deletes Adware, Toolbars, Potentially Unwanted Programs (PUP), and browser Hijackers from your computer. By using AdwCleaner you can easily remove many of these types of programs for a better user experience on your computer and while browsing the web.
I was trying to access the shadow copies of one of these folders after the user has been deleted, I was trying to take ownership of the shadow copies folder so we can restore some data that was in there but every time I try take ownership of the folder I get a “Media is Write Protected” message and everything we have tried to do involving taking over the shadow copy has failed.
download dosdev if you don’t have it from http://vscsc.sourceforge.net/ then mount the shadow copy as V drive then use robocopy to copy the file to different location on current time, then take ownership of files.
C:\resources\dosdev\dosdev\x86>vssadmin list shadows
Contents of shadow copy set ID: {85e1a1e5-e6dd-4479-ab11-769930317777} Contained 1 shadow copies at creation time: 1/28/2014 7:00:06 AM Shadow Copy ID: {c152023d-6a53-46a5-ae90-eac06d7b1f0d} Original Volume: (S:)\\?\Volume{1d09abf5-50bb-4619-ae1a-582285e37e1f}\ Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy260 Originating Machine: MACSRVR.mac.macltd.com Service Machine: MACSRVR.mac.macltd.com Provider: ‘Microsoft Software Shadow Copy provider 1.0’ Type: ClientAccessible Attributes: Persistent, Client-accessible, No auto release, No writers, Differential Contents of shadow copy set ID: {b1ceef12-fa9a-4aae-961a-1212df929c27} Contained 1 shadow copies at creation time: 1/28/2014 12:01:05 PM Shadow Copy ID: {eb169c0f-373d-4431-9ea3-e97d22f8fe7d} Original Volume: (S:)\\?\Volume{1d09abf5-50bb-4619-ae1a-582285e37e1f}\ Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy263 Originating Machine: MACSRVR.mac.mactd.com Service Machine: MACSRVR.mac.macltd.com Provider: ‘Microsoft Software Shadow Copy provider 1.0’ Type: ClientAccessible Attributes: Persistent, Client-accessible, No auto release, No writers, Differential C:\resources\dosdev\dosdev\x86>
There is bit more you can do with robocopy the files from your shadow copy.
One of my client had Crypto Locker virus with extension .zepto and encrypted all the files in shared drive. This is what I have done to recover, first logged on to the server did a search for *.zepto on the top level drive, in my case it was D:\ then I copied the search result to text file, it sound simple to copy search result to text file, if you haven’t done this before then how do you do it. You select the first line of search scroll to last line then ->hold shift and right click -> you get drop down menu select “Copy as Path” then you can open a notepad and paste.
now you have all the path in text file. using the dosdev process as above, I mounted the shadow copy that I want to copy from then run the robocopy command as below,
What this does is check all files and folder copy anything missing or different. I tried going to previous version in windows and browsing the copy then copy the file I needed but for this huge amount of data 10TB, didn’t wanted to do folder by folder also when it hit long file name or path then it stop copying, robocopy is the only way I found to be accurate.
Then I gone back to my search and deleted all the files that ware highlighted.
or you can use command prompt
c:\>del *.zepto /a /s
Spotlight works great most of the time, but occasionally you may need to do a bit of tinkering to get it to work properly. Most of us have probably had a problem where Spotlight won’t find a file you know is there. Here are a few Terminal commands for changing hidden Spotlight settings, performing more complicated searches and updating.
Add a file to the Spotlight index
Type in mdimport and then hit the space bar. Next, find the file you want to add in the Finder, and drag it onto the Terminal window.
Add a folder to the Spotlight index
In that case use mdimport -f instead. You might want to use this to add the System folder with mdimport -f /System as it isn’t searchable by default. In 10.7.5, “The -f option has been obsoleted and does nothing.
Search Spotlight from the Terminal
To do a search, just type mdfind query where query is what you want to search for. To limit this to a specific folder, instead use mdfind -onlyin ~/Desktop query replacing~/Desktop with the path to your folder. To run a “live” search which will update the results as users add files, use mdfind -live query. Control-C will stop it updating. To see all the other options, look at the man page by typing man mdfind into Terminal.
Re-index an entire drive
In the Terminal, type sudo mdutil -E / and hit return. You may have to enter your password. The existing Spotlight index will be deleted, and Spotlight will start creating a new index in the background. You can re-index other hard drives by changing the command to include their name, like sudo mdutil -E /Volumes/OtherHardDrive.
sudo mdutil -i off /
sudo rm -rf /.Spotlight*
sudo mdutil -i on /
sudo mdutil -E /
1 – turn indexing off
2 – delete Spotlight folder
3 – turn indexing on
4 – rebuild
Does this help?
Very Useful
Also you could use these commands:
sudo mdutil -a -i off
sudo mdutil -a -i on
Flushing your cache and rebuilt it with the following command: sudo mdutil -pEsav
I had the exact same problem, with all solutions above failing identically. Then I reexamined the directory listing for / and found a hidden file .metadata_never_index in the root directory. I removed this file and was able to turn spotlight on again with mdutil -i on /.
mds is now reindexing the hard disk, all looks good for now.
In terminal, I ran “mdutil -sa” that shows whats indexed
Also I have seen most of the above command-lines would produce 'Indexing and searching disabled'. sudo mdutil -pEsav gave me 'datastore publishing not implemented.'
Below is the solution that worked:
edit /etc/hostconfig
add the line SPOTLIGHT=-YES- at the bottom (this line was missing)
Enable-ExchangeCertificate : The certificate with thumbprint XXXXXXX was found but is not valid for use with Exchange Server
(reason: PrivateKeyMissing).
At line:1 char:27
+ Enable-ExchangeCertificate -Thumbprint XXXXXXXXX -Services "IIS"
The above error can as a result of multiple reasons. CSR was created with IIS and attempted to be installed through the Exchange Management Shell (EMS), CSR was created in EMS on another Exchange Server, a damaged certificate, or Windows simply “forgets” where it placed the PrivateKey for the certificate. It doesn’t happen all the time, but sometimes the error can be a nuisance.
Option #1: Repair Damaged Certificate (Windows Server 2003/2008)
Open MMC and add the Certificate Snap-In for the Local Computer account.
Double-Click on the recently imported certificate.
Note: In Windows Server 2008 it will be the certificate missing the golden key beside it.
Select the Details tab.
Click on the Serial Number field and copy that string.
Note: You may use CTRL+C, but not right-click and copy.
Open up a command prompt session. (cmd.exe aka DOS Prompt)
Type: certutil -repairstore my “SerialNumber” (SerialNumber is that which was copied down in step above.)
After running the above command, go back to the MMC and Right-Click Certificates and select Refresh (or hit F5 in the MMC)
Double-Click on the problem certificate. At the bottom of this window (General tab) it should state: “You have a private key that corresponds to this certificate.“
Note:
In Windows Server 2008 there will be a golden key to the left of the certificate, so there is no need to double-click the certificate.Now that the Private Key is attached to the certificate, please proceed to enable Exchange Services via
When I click Configure Remote Desktop from the Server Manager the Remote Tab opens under System Properties. The problem is all I see is Remote Assistance and not the Remote Desktop portion (See Picture). Why is this missing, this is the only server in random that has this problem.
(How it should look Below)
SOLUTION:
For my surprise this due to a problem with the product key. I re-enter the proper product key for this server and activate. This is done in Control Panel — System and Security — System, click on Change product key, and follow the wizard. I didn’t needed to restart after activating for the Remote Desktop options to show up.
And if you are missing the top part i.e Remote Assistance, for that you will need to install the feature.
After upgrading Exchange 2010 SP3 on Windows 2008 Enterprise Server with SP2. when I open the exchange management shell or try to access the Queue Viewer via the Exchange Managment Console I get the following error and I can’t run any commands in the Exchange Management Shell or in the PowerShell.
The term ‘C:\Program Files\Microsoft\Exchange Server\V14\\bin\RemoteExchange.ps
1’ is not recognized as the name of a cmdlet, function, script file, or operabl
e program. Check the spelling of the name, or if a path was included, verify th
at the path is correct and try again.
At line:1 char:2
+ . <<<< ‘C:\Program Files\Microsoft\Exchange Server\V14\\bin\RemoteExchange.p
s1’; Connect-ExchangeServer -auto
+ CategoryInfo : ObjectNotFound: (C:\Program File…oteExchange.p
s1:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
The term ‘Connect-ExchangeServer’ is not recognized as the name of a cmdlet, fu
nction, script file, or operable program. Check the spelling of the name, or if
a path was included, verify that the path is correct and try again.
At line:1 char:99
+ . ‘C:\Program Files\Microsoft\Exchange Server\V14\\bin\RemoteExchange.ps1’; C
onnect-ExchangeServer <<<< -auto
+ CategoryInfo : ObjectNotFound: (Connect-ExchangeServer:String)
[], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
SOLUTION:
This is what I have done to fix my issue.
Checked to see if I have all these scripts in your bin (C:\Program Files\Microsoft\Exchange Server\V14\\bin\) folder and they ware missing, I copied them there from the install media (Extracted Exchange SP3) under \setup\serverroles\common:
Copy Receive Connectors from one Exchange Server to another
When doing migration creating new Exchange Receive Connectors that has alot of IP Addresses.
Doing this manually is a pain! But there is a command we can use to accomplish this
CAS1 is the server that I will copy the Receive Connector and CAS2 the new server and name of receive connector is “my connector” where I will create the same connector as showing on the CAS1:
