ahh cool. So may ways to do things, wouldn't have thought about using a compliance rule for this. Thanks!
On Tue, Feb 2, 2016 at 9:53 AM, Jerousek, Jeff <[email protected]> wrote: > Compliance setting to change it, and verify that it was changed. > > > > Thanks, > > Jeff Jerousek > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *ccollins9 > *Sent:* Tuesday, February 2, 2016 8:39 AM > > *To:* mssms <[email protected]> > *Subject:* Re: [mssms] RE: IE shortcut URL deployment? > > > > You used compliance settings to change it, or just to verify that it was > changed by an application or GPO? > > > > On Tue, Feb 2, 2016 at 9:33 AM, Jerousek, Jeff <[email protected]> > wrote: > > If you want to track it use a compliance setting. > > > > I used one to switch everyone’s Start Menu .urls to a new site. > > > > Thanks, > > Jeff Jerousek > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *ccollins9 > *Sent:* Tuesday, February 2, 2016 8:22 AM > *To:* mssms <[email protected]> > *Subject:* Re: [mssms] RE: IE shortcut URL deployment? > > > > Yes, no real way to track or verify like with the discovery criteria in > SCCM. For us, we use custom made icons for some shortcuts that aren't on > the native OS. So if we use GPO we'd have to either keep that icon shared > in a central location and point the policy to it, or deploy the file to the > machine and point the policy to it locally. I'd rather just use SCCM in > that case. > > > > On Mon, Feb 1, 2016 at 8:14 PM, Jason Sandys <[email protected]> wrote: > > Don’t disagree. There’s no way to track it though or know if it truly > worked. > > > > J > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Taxter, Latisha > *Sent:* Monday, February 1, 2016 3:40 PM > > > *To:* [email protected] > *Subject:* [mssms] RE: IE shortcut URL deployment? > > > > Still thinks gpo is pretty quick. User, Preferences, shortcuts. Select > Target typeURL, Item level targeting – domain users or whatever AD group > you choose It’s a lot less work than maintaining a deployment. Nothing > against SCCM. I love it for everything else. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Monday, February 1, 2016 10:54 AM > *To:* [email protected] > *Subject:* [mssms] RE: IE shortcut URL deployment? > > > > This is a pretty easy task. Create the .lnk or .url file, create a batch > file to copy the .lnk (or .url) file to the public desktop folder, place > both in a package, run the batch file in the program. Done. > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Gerding, Matt > *Sent:* Monday, February 1, 2016 1:27 PM > *To:* [email protected] > *Subject:* [mssms] RE: IE shortcut URL deployment? > > > > Yeah, I think I will use GP for this. I just finished discussing my > options with someone else and it sounds like deploying shortcuts via SCCM > can be a bit cumbersome. Thanks for the quick response. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Taxter, Latisha > *Sent:* Monday, February 1, 2016 1:13 PM > *To:* [email protected] > *Subject:* [mssms] RE: IE shortcut URL deployment? > > > > Are you opposed to using a group policy? I deploy all my shortcuts with > GPO > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Gerding, Matt > *Sent:* Monday, February 1, 2016 9:58 AM > *To:* [email protected] > *Subject:* [mssms] IE shortcut URL deployment? > > > > Does anyone know of a simple way to deploy an IE shortcut URL with SCCM > 2012 R2 to the all users desktop for client machines running Windows 7? > > > > Thanks, > > > > [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > >
