@Eric-Ross said in CentOS 7 VM won't boot after migration to Proxmox:

@JaredBusch Ah, too bad that wasn't the fix.

I didn't bother at the dracut point. I likely could have recovered the system. I simply decided to stop putting off the migration of those workloads.

They were still running CentOS 7 after all.

Have you tried the linux Icloud Photo downloader?

https://github.com/ndbroadbent/icloud_photos_downloader

Or installing Icloud for Linux and then mounting the photo space?
sudo snap install icloud-for-linux

If I recall, the drive folder is here, photos can't be too terribly different
~/Library/Mobile\ Documents/com~apple~CloudDocs/

@wrx7m said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@black3dynamite said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@wrx7m said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@dafyre said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@dafyre said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@pmoncho said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@wrx7m

Just curious, when you chose UPD, did you choose to store all settings or just certain folders?

Some applications don't play nicely with roaming profiles.

UPDs mount at the usual C:\Users\user.name and the applications can't tell a difference.

Right. But, only when the user is logged in. After they logout, that path doesn't exist. I am trying to figure out how to work around that for adding the custom (for each user) erp shortcut on their desktop in their session.

Add the shortcut to C:\Users\Public\Desktop.
That way it will always show up on each user Desktop.

This would be nice and easy, but each user has a custom shortcut- It has a workstation ID in the target path.

https://www.pdq.com/blog/pdq-deploy-and-powershell/
Create a script that creates the shortcut each user Desktop and append the workstation id in the target path.

Fixed a small typo.

@IRJ This would be a heck of a guide if you ever get the time to do it

@Obsolesce said in Hyper-V Node Failover Cluster Control:

@JaredBusch said in Hyper-V Node Failover Cluster Control:

@Obsolesce said in Hyper-V Node Failover Cluster Control:

@DustinB3403 said in Hyper-V Node Failover Cluster Control:

How can I migrate my VM's from Host 1 to Host 2 and ensure that the VMs don't attempt to automatically migrate back to their preferred host?

Migration? It's definitely not automatic in the least.

Planned failover? There's a checkbox to uncheck if you don't want automatic reverse replication and the VM to automatically start up. Could that be what you meant?

Of course it is. In an actual cluster. Which involves System Center Configuraiton Manager (SCCM).

@DustinB3403 used the word cluster, but he does not have one.

Oh shit, I missed that it was about a cluster. I was thinking Hyper-V Manager, right-click, live migration. Totally spaced there.

Yeah, that was my point, it is not a cluster.

I've have used that ProfileWiz before by ForensiT, works really well.

@bbigford said in How would you move an IIS workload from on site to a VPS:

I'll have to look into that, as I'm not sure how I can just copy the application folder though since it's an install on Windows.

Normally it is just a folder that contains the app. Presumably the app needs a datasouce as well, though. Where is that located?

What kind of web app is this? ASP.NET? PHP? Java?

This is timely.
THanks

@fateknollogee said in how do I migrate my KVM settings to a new desktop:

Can you "virsh dumpxml vmname" while the vm is running?

Yes.

qemu-img is actually what HyperCore OS uses internally when it is doing both import and export of VM's to/from HC3. As a result, if you use the "foreign VM import" process referenced above, it leverages the fact that if you simply rename a vmdk for example to a qcow2 file extension (that HC3 expects) and then import it, qemu-img will actually detect that the disk contained in file is really a VMDK and do that conversion automatically for you saving a step!

One other benefit of letting HC3 do the conversion is that it will convert to the right qcow2 format for that HC3 version automatically. if you are doing the pre-conversion using qemu-img on windows (or linux for that matter), you may want to run the qemu-img info on an empty HC3 exported qcow to see what flags it has and try to match them. depending on the version of HC3 and version of qemu for windows you are using I have seen cases mostly with older versions of HC3 where you need to specify the compat version to match something like this:

qemu-img convert -p -O qcow2 -o preallocation=metadata,compat=0.10 source-image.qcow2 output-image.qcow2

(this was an older version of HC3)

On a very new version of HC3 as of this post it looks like compat: 1.1. I got tired messing with stuff like that and the extra step so now I always start with renaming the virtual disk files to .qcow2 extension and try letting HC3 figure it out first at least which generally works. (VHDX may be the exception ... and of course you have to get into the "right" vmdk format in some cases as there are lots of different vmdk formats)

Another tip / FAQ - if you ever have a .OVA file, generally a virtual appliance, that is just a tar archive that you can expand and inside there will be a virtual disk file, usually .vmdk but sometimes .img format that you can convert/import into HC3 using the above processes.

Of course ALL of this is just getting HC3 to see the virtual disk. The OS on that virtual disk has to have the right drivers_ active_ to be able to boot on HC3 which either means that it has virtio drivers pre-installed and set to boot (if "performance" drivers are selected when creating the VM) or IDE drivers (if "compatible" drivers are selected ... and for windows mergeide.reg was run before migration.) Linux is generally just automatic but Windows will result in a 7B BSOD if a driver for the boot disk isn't active on the imported virtual disk.

@dustinb3403 said in Exchange migrations, scenarios to hope you're never in.:

User abuse is the only bug we can't fix with technology.

Good to know eseutil was able to correct the issue.

Even that was just very weird. The status had stopped updating and processes associated with it quit doing anything for around 20 minutes. We were both wondering what was going on when I was like "I'm going to ctrl+c it." So the cancel current command actually kicked off a whole bunch of activity that went quite quickly compared to what it had been running at before and actually repaired the DB. We were both more than a little confused over that one.

Sorry, he posted that for me and no I did not see that. I think that is a good answer on what to do and will go forward from there. Thanks.

@dashrender It is SA

Maybe this earlier discussion will help.
https://www.mangolassi.it/topic/13392/import-xenserver-export-into-scale-cluster

@JaredBusch said in SSH Keys and migrating to a new device:

@wirestyle22 said in SSH Keys and migrating to a new device:

@JaredBusch Thanks. This is great

Again, you want a unique private key on every device, in order to lock things out discretely. Otherwise if you simply had the same private key everywhere, you would lose all access form every device just because your laptop was compromised and you had to lock out the public key.

So this process is really only something that should ever happen on a profile migration.

Ya it's a big advantage to having automounted home directories or having LDAP store the keys. You can easily revoke and add another key and have it work everywhere.

Or using Kerberos instead of pub/priv keys.

I realize @JaredBusch knows this, but for others who may not.

@DustinB3403 said in Print Services - Migrate from one server to another:

@IRJ people have a hard time reading labels that could save their life, I don't expect my users to read any announcements coming from IT.

Edit: mostly because I know they don't care, they just need it to work.

^ this, so much this!

My users only read my email today because they already knew the phones were having issues, and now they knew that I also knew. But a future notice, they won't remember for the most part 20 mins from now 😛

it's all good, again, mostly just flipping shit.

You can use the upgrade tool which is even easier if you are on a current version of owncloud. Even though the article doesn't say anything about updating from owncloud, the first article I posted does say you can use this method on current owncloud servers. You just switch the update channel and search for updates.

https://nextcloud.com/blog/get-up-to-date-with-the-new-nextcloud-updater/