Isn’t Quicktime pretty much useless with Windows 10?
From the Quicktime page:
Important: QuickTime 7 for Windows is no longer supported by Apple. New versions of Windows since 2009 have included support for the key media formats, such as H.264 and AAC, that QuickTime 7 enabled. All current Windows web browsers support video without the need for browser plug-ins.
@twilems No idea. If the cause is the same, then probably.
@twilems Just run it. It will fix the issue for all users.
@kafluke fog.log is found at C:\
Sounds like an issue with the FOG client?
Check to see if the FOGService is running. Then toggle it off/on. It should resume working. If not, check the fog.log.
@mwarner said in Microsoft Surface Pro 4:
@sebastian-roth Here is the link to a .pcap file of the surface in question trying to connect. The surface itself loads the FOG menu properly and successfully, as shown by the .pcap, but when I selected the “Perform Full Host Registration” option it seems to recognize that there’s an error with the ethernet connection. Perhaps you could provide some more insight?
Are you willing to purchase a different USB NIC?
The Microsoft Surface dongle model# 1663 has been confirmed to work. Alot of the other docks/usb nics don’t work.
@obsidian said in Can I join a pc to the domain using fog but not using a fog image:
Okay thanks I was thinking that it might. I am going to start testing this now to see if I can get it to work. Do I need the fog agent installed or just to register it with the fog server?
If the hostname is already correct on the PC, I’d suggest just installing the FOG Client and letting it auto register to the server. You can manually register the client though as long as you have the MAC address.
You may have better luck using a .cmd file and using something like:
net user <username> <password> /ADD
I’ve seen similar issues posted regarding trying to do this via PowerShell as a snapin.
I’ve seen the article where those additional files were listed; however, they were not present on our systems so they were not included in the fix.
I deployed the solution posted above via SCCM to all Windows 10 systems and it’s solved our issues.
Better fix:
The following PowerShell snippet appears to fix the previously reported issues that appeared after the Feature Update to Build 1703.
# Removes WebCache and INetCache folders from Default Profile.
Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache -Force -Recurse
Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache -Force -Recurse
$Users = (Get-ChildItem -Path "$env:SystemDrive\Users").FullName
# Deletes WebCache and INetCache on all non-hidden users.
ForEach($User in $Users) {
Remove-Item -Path $User\AppData\Local\Microsoft\Windows\WebCache -Force -Recurse -ErrorAction SilentlyContinue
Remove-Item -Path $User\AppData\Local\Microsoft\Windows\INetCache -Force -Recurse -ErrorAction SilentlyContinue
}
This fixes it for all new and existing user profiles.
In case anyone else experience this issue, we seem to have a solution. Something corrupted the default user profile during the Feature Update from Build 1607 to Build 1703.
The following PowerShell commands took care of the issue:
Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache -Force -Recurse
Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache -Force -Recurse
This solves the issues for any new profiles, but profiles created after the Feature Update will need to be deleted.
This can be marked as solved now.
@Oasis So, just from experience, this probably isn’t going to work the way you want to.
Get-AppxPackage will only return AppxPackages that the user running the command has (SYSTEM). It will also only be removing them from the SYSTEM profile… which won’t really do anything.
You’ll want to add the AllUsers flag.
Get-AppxPackage -AllUsers | Where-Object -Property Name -Match <packagename> | Remove-AppxPackage
Or maybe this might work?
Get-AppxPackage -AllUsers | Where-Object -Property Name -Match <packagename> | Remove-AppxPackage -AllUsers
@x23piracy Thanks. There was some useful information on there.
This is not a FOG issue, but hoping someone might know something.
The image I build and deployed this summer was Windows 10 Enterprise Build 1607. A few weeks back our machines started updating to Build 1703.
This is only affecting users who did not have a profile on the PC prior to the update. On these machines the Start menu freezes, especially if you attempt to type/search. Some applications also won’t load or become unresponsive while loading.
I’m thinking it may have something to do with AppxPackages and/or AppxProvisionedPackages that were removed on the original image. After the Build 1703 update, many (maybe all) of the AppxPackages and AppxProvisionedPackages that I had removed were restored… which was really irritating.
I’ve had it happen where the service appears to be running, but it’s not actually working. I had to re-install the FOG client.
@jay-bosworth said in Windows 10 EDU 1709 Domain Join Doesn't Work:
[https://pastebin.com/rAhGAr4L](link url)
Couple things.
Biggest issue here seems to be the client not being able to authenticate with the server. On your host(s), press the “Reset Encryption Data” button if it’s there. That may solve your issue entirely.
Other issues, both your FOG version and client are outdated. The people here always suggest updating, so that’s what I’m going to say.
@jay-bosworth said in Windows 10 EDU 1709 Domain Join Doesn't Work:
I just re-imaged it at 11:15 EST. The contents of the fog.log file is too large to post here so I am going to upload the file.[0_1510676495784_fog.log](Uploading 100%)
Use something like https://pastebin.com/
@astrugatch said in [help] PXE for UEFI devices:
undionly.kpxe
Change Option 67 from undionly.kpxe to ipxe.efi should be all you need for just UEFI booting, I think.
@zago123 said in Service Fog Client:
why? what would be the problem of letting him get started?
The problem is when the client starts reaching out to the FOG server before Windows is completely done getting ready. The client can cause the host to reboot before Windows is finished setting up… which is a bad thing.
I believe the latest SmartInstallers have the FOG Service start type set to manual by default.
If I’m understanding this correctly, you want a way to add/update the inventory without pxe booting?
That would actually be incredibly useful to me too. This summer I switched my site over to a different server for imaging, but the client still pointing to the ‘main’ server. All the inventory data was registered to the test server and I just imported the hosts into the main server. Didn’t get the hardware info on any of the new stuff.