If you want to continue down this path of PSEXEC, how about having an python agent that tracks your changes, check SaltStack, and salt minion, it will make your life alot easier, and it is much modern and supported than PSEXEC
AT&T is definitely blowing smoke. The new tenant will "own" that IP equipment and can charge both the existing tenant and AT&T for use of the facilities, or just cut it off. The new tenant will own that equipment and that connection.
So until you can show us what you are talking about, please answer this...
Why does he? As I illustrated in a prior post anyone can spam anything all day long. Why does he care about these bad accounts?
Yes, and arent these reports detailing hundreds or thousands of bad email addresses/day? Seems like they would be. If i received this report it would have tens of thousands of bad address bounce messages every single day.
In a large org i imagine it would be many millions.
I went with Lubunutu in the end. The hardware I have is old, but not ancient. Centrino 2 and 3 gb of RAM. I tried puppy linux and bodhi linux, but didn't care for either.
Puppy was fast, but ugly as holy hell. Bodhi didnt seem to work right on my system. It was sluggish for some reason.
Ya Puppy is just bad. I hadn’t Slitaz running on an old thin client at one point. It worked pretty well for that.
I didn't see your reply until after I decided on Lubuntu. I will try a Slitaz on a usb drive.
Ya I didn’t mean for you to have to do that. It’s ok, doesn’t look awesome but def looks better than Puppy.
I dont feel obligated. I just want to give it a shot 🙂
PS C:\Users\aolynyk\Desktop> C:\Users\aolynyk\Desktop\Repair-SophosUpdate.ps1
cmdlet Repair-SophosUpdate at command pipeline position 1
Supply values for the following parameters:
computername: localhost
Restart-Service : Cannot find any service with service name 'System.ServiceProcess.ServiceController'.
At C:\Users\aolynyk\Desktop\Repair-SophosUpdate.ps1:16 char:13
+ Restart-Service -Name $Service -PassThru -Verbose -Force
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (System.ServiceProcess.ServiceController:String) [Restart-Service], ServiceCommandException
+ FullyQualifiedErrorId : NoServiceFoundForGivenName,Microsoft.PowerShell.Commands.RestartServiceCommand
I can restart the services as an admin but when I run the script as an admin I get the same error
PS C:\WINDOWS\system32> Restart-Service 'Sophos Agent' -PassThru
Status Name DisplayName
------ ---- -----------
Running Sophos Agent Sophos Agent
PS C:\WINDOWS\system32> Restart-Service 'Sophos Message Router' -PassThru
Status Name DisplayName
------ ---- -----------
Running Sophos Message ... Sophos Message Router
PS C:\WINDOWS\system32>
Sadly I don't do anything with oVirt. I run OpenStack at home and bare KVM at work.
SOrry, I thought you were doing oVirt stuff. my bad.
No prob. I think @Tim_G was doing something with it. I just find it too bloated. It’s pretty sad whenever it’s easier to do an all in one OpenStack than it is to do oVirt.
works perfectly when one specifies the correct data directory on the source.
/home/owncloud/data/
sent 1764471 bytes received 178175 bytes 56308.58 bytes/sec
total size is 148236697158 speedup is 76306.59 (DRY RUN)
I hate that. You always have a few outliers before you standardize on things and they are always the gotchas. This has happened to me on many occasions.
@jaredbusch Right, I get that. I meant that they should still exist once I activate the new install since they were in the DB that was backed up on the old install and restored on new.
AH, I missed the part about having made a backup and restore.
@fredtx did you reboot after clearing those keys? I’m not using workspaces anyplace at the moment to try and test this.
Yes I did. This may be from the aftermath from last Friday where I had to fix the RD Broker that wasn't allowing new remote apps on "any" workstation. Couldn't even access rd web from the broker itself. I had to give full access to IIS_URS and Network Service groups for both Tempasp.net files and c:\windows\temp folders. Restart IIS and that fixed the company wide issue. However, this 2 computers are giving me issues still.